From: Rob Browning <rlb@defaultvalue.org>
Cc: emacs-devel@gnu.org
Subject: Re: m68k "Invalid character:" build failure look familiar to anyone?
Date: Fri, 26 Sep 2003 11:57:05 -0500 [thread overview]
Message-ID: <87wubvzdwe.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <jwv65jfpm6b.fsf-monnier+emacs/devel@vor.iro.umontreal.ca> (Stefan Monnier's message of "26 Sep 2003 12:09:51 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> 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,
Certainly, though it gives me an error:
$ EMACSLOADPATH=/home/rlb/tmp/emacs21-21.3+1/lisp \
../src/bootstrap-emacs --no-site-file --multibyte
(setq debug-on-error t)
t
(setq byte-compile-debug t)
t
(byte-compile-file
"/home/rlb/tmp/emacs21-21.3+1/lisp/emacs-lisp/byte-opt.el")
At this point emacs beeps and prints "Attempt to split fixed-size
window" in the minibuffer. I get the same result if I just try M-x
debug after firing up bootstrap-emacs.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2003-09-26 16:57 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
2003-09-26 16:57 ` Rob Browning [this message]
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=87wubvzdwe.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).