--- Begin Message ---
Subject: |
"Wrong type argument: characterp" building custom-deps while boostrapping |
Date: |
Sat, 19 May 2012 18:10:07 +0200 |
Package: emacs
Version: 24.1.50
With current trunk (revno:108308) bootstrapping on Windows throws an
error while building custom-deps:
make -w cus-load.el-CMD
make[2]: Entering directory `C:/emacs/debug/lisp'
echo ;;; cus-load.el --- automatically extracted custom
dependencies> cus-load.el-CMD
echo ;;>> cus-load.el-CMD
echo ;;; Code:>> cus-load.el-CMD
echo.>> cus-load.el-CMD
echo ;; Local Variables:>> cus-load.el-CMD
echo ;; version-control: never>> cus-load.el-CMD
echo ;; no-byte-compile: t>> cus-load.el-CMD
echo ;; no-update-autoloads: t>> cus-load.el-CMD
echo ;; End:>> cus-load.el-CMD
make[2]: Leaving directory `C:/emacs/debug/lisp'
mv cus-load.el-CMD C:/emacs/debug/lisp/cus-load.el
Directories: calc calendar emacs-lisp emulation erc eshell gnus
international language mail mh-e net nxml org play progmodes textmodes
url vc cedet ce
"../src/oo/i386/emacs.exe" -batch --no-site-file --no-site-lisp -l
cus-dep --eval "(setq find-file-hook nil)" \
-f custom-make-dependencies
C:/Devel/emacs/repo/debug/lisp calc calendar emacs-lisp emulation erc
eshell gnus international language
Directory C:/emacs/debug/lisp
Directory calc
Directory calendar
Directory emacs-lisp
Directory emulation
Directory erc
Directory eshell
Directory gnus
Directory international
Directory language
Wrong type argument: characterp, 4195283
make[1]: [custom-deps] Error -1 (ignored)
rm "../src/oo/i386/emacs.exe"
After bootstraping,
cd lisp
make custom-deps
works as expected.
The error appeared somewhere in the past ten days or so (I have a
bootstrap log from 2012-05-08 which does not show the problem).
Juanma
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#11519: "Wrong type argument: characterp" building custom-deps while boostrapping |
Date: |
Sat, 28 Dec 2013 11:48:26 +0200 |
> From: Glenn Morris <address@hidden>
> Cc: Juanma Barranquero <address@hidden>, address@hidden
> Date: Sat, 28 Dec 2013 03:41:32 -0500
>
>
> Is this report still relevant?
No. Closing.
--- End Message ---