From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Feng Li <fengli@gmail.com>, emacs-devel@gnu.org
Subject: Re: about the byte-opt.el patch
Date: Thu, 05 Jul 2007 22:46:46 +0200 [thread overview]
Message-ID: <873b02tw7d.fsf@ambire.localdomain> (raw)
In-Reply-To: <jwvmyyan54p.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu\, 05 Jul 2007 13\:17\:10 -0400")
() Stefan Monnier <monnier@iro.umontreal.ca>
() Thu, 05 Jul 2007 13:17:10 -0400
> with env var "CVSREAD" set to "1" and
That's the problem. [...] Autoload entries can now be redirected to
some other file, so ps-mule.el's autoloads end up in ps-print.el
(where they used to be written by hand instead), and similarly for
cl-*.el which end up in cl-loaddefs.el.
grumble.
ok, now w/ the latest Makefile.in (which does chmod +w on those files),
i am able to build from "make bootstrap" and:
- not reproduce the crash w/ byte-opt.el pre-change
- yes reproduce the crash w/ byte-opt.el post-change
i have reverted byte-opt.el. to OP: sorry for the noise. please
disregard previous requests for additional info (but feel free to
share any insights you have on the problem, anyway :-).
thi
next prev parent reply other threads:[~2007-07-05 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 0:04 about the byte-opt.el patch Feng Li
2007-07-05 12:54 ` Richard Stallman
2007-07-05 16:19 ` Thien-Thi Nguyen
2007-07-05 17:17 ` Stefan Monnier
2007-07-05 20:46 ` Thien-Thi Nguyen [this message]
2007-07-06 9:50 ` Eli Zaretskii
2007-07-06 11:00 ` Thien-Thi Nguyen
2007-07-06 13:03 ` Stefan Monnier
2007-07-06 10:53 ` File-specific autoloads (was: about the byte-opt.el patch) Eli Zaretskii
2007-07-06 14:02 ` File-specific autoloads Thien-Thi Nguyen
2007-07-06 16:04 ` Eli Zaretskii
2007-07-06 18:28 ` Thien-Thi Nguyen
2007-07-07 1:32 ` Stefan Monnier
2007-07-07 10:16 ` Eli Zaretskii
2007-07-07 4:55 ` Stefan Monnier
2007-07-07 10:43 ` Eli Zaretskii
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=873b02tw7d.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=fengli@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).