From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: m68k "Invalid character:" build failure look familiar to anyone?
Date: 26 Sep 2003 12:09:51 -0400 [thread overview]
Message-ID: <jwv65jfpm6b.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (raw)
In-Reply-To: <87smmmoilt.fsf@raven.i.defaultvalue.org>
> During a full boostrap build, the build fails as follows:
> for el in /home/rlb/tmp/emacs21-21.3+1/lisp/emacs-lisp/byte-opt.el /home/rlb/tmp/emacs21-21.3+1/lisp/emacs-lisp/bytecomp.el /home/rlb/tmp/emacs21-21.3+1/lisp/subr.el /home/rlb/tmp/emacs21-21.3+1/lisp/progmodes/cc-mode.el /home/rlb/tmp/emacs21-21.3+1/lisp/progmodes/cc-vars.el $els; do \
> echo Compiling $el; \
> EMACSLOADPATH=/home/rlb/tmp/emacs21-21.3+1/lisp ../src/bootstrap-emacs -batch --no-site-file --multibyte -f batch-byte-compile $el || exit 1; \
> done
> Compiling /home/rlb/tmp/emacs21-21.3+1/lisp/emacs-lisp/byte-opt.el
> !! error (("Invalid character: 037000000000, -134217728, 0xf8000000"))
> !! error (("Invalid character: 037600000000, -33554432, 0xfe000000"))
> !! error (("Invalid character: 037300000000, -83886080, 0xfb000000"))
> !! error (("Invalid character: 037500000000, -50331648, 0xfd000000"))
> !! error (("Invalid character: 037200000000, -100663296, 0xfa000000"))
> !! error (("Invalid character: 037100000000, -117440512, 0xf9000000"))
> While compiling toplevel forms in file /home/rlb/tmp/emacs21-21.3+1/lisp/emacs-lisp/byte-opt.el:
> !! error (("Invalid character: 037600000000, -33554432, 0xfe000000"))
> !! error (("Invalid character: 037500000000, -50331648, 0xfd000000"))
> !! error (("Invalid character: 037200000000, -100663296, 0xfa000000"))
> !! error (("Invalid character: 037500000000, -50331648, 0xfd000000"))
> !! error (("Invalid character: 037100000000, -117440512, 0xf9000000"))
> !! error (("Invalid character: 037600000011, -33554423, 0xfe000009"))
> !! error (("Invalid character: 037600000000, -33554432, 0xfe000000"))
> Done
> make[3]: *** [compile-files] Error 1
Could you use ../src/bootstrap-emacs interactively and byte-compile the
file from there, while setting both debug-on-error and byte-compile-debug
to a non-nil value ?
This should give you a lisp backtrace,
Stefan
next prev parent reply other threads:[~2003-09-26 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 5:34 m68k "Invalid character:" build failure look familiar to anyone? Rob Browning
2003-09-24 9:06 ` Andreas Schwab
2003-09-24 23:22 ` Rob Browning
2003-09-25 9:01 ` Andreas Schwab
2003-09-25 15:30 ` Rob Browning
2003-09-25 16:12 ` Andreas Schwab
2003-09-25 16:28 ` Rob Browning
2003-09-25 17:33 ` Kevin Rodgers
2003-09-26 9:16 ` Andreas Schwab
2003-09-26 14:17 ` Rob Browning
2003-09-26 16:09 ` Stefan Monnier [this message]
2003-09-26 16:57 ` Rob Browning
2003-09-27 16:46 ` Rob Browning
2003-09-27 16:59 ` Rob Browning
2003-09-29 14:28 ` Stefan Monnier
2003-09-29 16:49 ` Rob Browning
2003-10-03 21:22 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv65jfpm6b.fsf-monnier+emacs/devel@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).