From: "Stuart D. Herring" <herring@lanl.gov>
Cc: emacs-devel@gnu.org
Subject: Re: erroneous byte-compilation during build process?
Date: Tue, 2 May 2006 12:46:47 -0700 (PDT) [thread overview]
Message-ID: <34798.128.165.123.132.1146599207.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <87hd48p6np.fsf@escher.local.home>
> Is my conclusion plausible? If so, is it cause for concern that there
> may be other erroneous byte-compiled files in the installation tree?
> And does this indicate a bug in the byte compiler, or could something
> else induce the error? The two recentf.elc files -- the one made by
> the build process and the one I byte-compiled from source -- differ in
> almost every line, as shown by diff -a, but I don't know what the
> differences mean: as far as I can tell, they only differ in cons cells
> like this:
>
> 19c19
> < (defvar recentf-list nil (#$ . 677))
> ---
> > (defvar recentf-list nil (#$ . 671))
If these are the only changes, they're entirely irrelevant; the numbers
just indicate the places in the file where the documentation can be found.
The difference is probably a difference in the length of the file name
given in the comment block at the top. Check for other differences, or
make the file/path names the same length for testing.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2006-05-02 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:29 erroneous byte-compilation during build process? Stephen Berman
2006-05-02 19:46 ` Stuart D. Herring [this message]
2006-05-02 21:56 ` Stephen Berman
2006-12-27 3:00 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34798.128.165.123.132.1146599207.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.