From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Feng Li <fengli@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: about the byte-opt.el patch
Date: Thu, 05 Jul 2007 18:19:27 +0200 [thread overview]
Message-ID: <87hcoilt68.fsf@ambire.localdomain> (raw)
In-Reply-To: <loom.20070705T015713-397@post.gmane.org> (Feng Li's message of "Thu\, 5 Jul 2007 00\:04\:30 +0000 \(UTC\)")
() Feng Li <fengli@gmail.com>
() Thu, 5 Jul 2007 00:04:30 +0000 (UTC)
I built emacs from the cvs trunk today
what commands did you use, precisely?
and it crashed at me on startup while
loading recentf-mode
with env var "CVSREAD" set to "1" and
using "cvs update
&& mv /tmp/byte-opt.el-1.94 lisp/emacs-lisp/byte-opt.el
&& ./configure --prefix ~/local
&& make clean
&& rm -f lisp/loaddefs.el
&& make bootstrap"
(these steps take into account the request by rms (in another message) to
revert byte-opt.el), i see a different error:
[...]
Generating autoloads for ps-bdf.el...
Generating autoloads for ps-bdf.el...done
Generating autoloads for progmodes/ps-mode.el...
Generating autoloads for progmodes/ps-mode.el...done
Generating autoloads for ps-mule.el...
Autoloads file /home/ttn/build/GNU/emacs/lisp/ps-print.el is not writable
make[2]: *** [autoloads] Error 255
make[2]: Leaving directory `/home/ttn/build/GNU/emacs/lisp'
at the time of error, there is not even a single .elc file in the tree,
so i surmise that if byte-opt.el is a problem, it is only the tail end
of a series of other problems. thus (to rms), i don't think reverting
it will be useful.
the message "Autoloads file .../ps-print.el is not writable" is strange;
the "autoloads file" should be loaddefs.el. sounds like some kind of
internal corruption.
can you do a fresh cvs update and build using the above steps? i'd like
to know if the error i see is reproducible. if not, could you describe
what you see?
thi
next prev parent reply other threads:[~2007-07-05 16:19 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 [this message]
2007-07-05 17:17 ` Stefan Monnier
2007-07-05 20:46 ` Thien-Thi Nguyen
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=87hcoilt68.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=fengli@gmail.com \
/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).