Re: ilisp build

"Steve Youngs" <youngs(a)xemacs.org&gt; writes: Thanks for the swift patch, unfortunately . . . I've just picked this up from CVS HEAD (a patch to the ilisp Makefile) but it fails to build with both xemacs 21.4.8 and 21.5-b6 (without mule, on a clean machine, no packages installed, using the latest release of cygwin on w2k). The original patch from Vin Shelton (using -batch-compile-file) worked fine for me; the CVS one (using -byte-compile-file) less so. I've appended the make output to the end of the message. // Conrad p.s. I'll try to stop finding problems soon. Promise? [snip successful build of the first part of the ilisp package] (cd extra; cp -f hyperspec-naggum.el hyperspec.el;true) xemacs-21.4.8 -no-autoloads -batch -l /home/src/xemacs/packages.r21-4-8/package-compile.el -- xemacs-base mail-lib fsf-compat eterm -- -f byte-compile-file extra/hyperspec.el Loading /usr/local/lib/xemacs-21.4.8/lisp/auto-autoloads... Loading /home/src/xemacs/packages.r21-4-8/xemacs-packages/eterm/auto-autoloads... Loading /home/src/xemacs/packages.r21-4-8/xemacs-packages/fsf-compat/auto-autoloads. .. Loading /home/src/xemacs/packages.r21-4-8/xemacs-packages/mail-lib/auto-autoloads... Loading /home/src/xemacs/packages.r21-4-8/xemacs-packages/xemacs-base/auto-autoloads ... # bind ( stack-trace-on-signal debug-on-signal stack-trace-on-error debug-on-error) signal(wrong-number-of-arguments (byte-compile-file 0)) # bind (data error-symbol) signal-error(wrong-number-of-arguments (byte-compile-file 0)) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Wrong number of arguments: byte-compile-file, 0 xemacs exiting .