From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 11649@debbugs.gnu.org
Subject: bug#11649: 24.1.50; Some compilation woes
Date: Thu, 14 Jun 2012 13:56:41 -0400 [thread overview]
Message-ID: <oiwr393hgm.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83aa05yg45.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 Jun 2012 20:10:02 +0300")
Eli Zaretskii wrote:
>> The "invalid byte code" errors.
>
> All I needed on GNU/Linux was this:
>
> make bootstrap
> cd lisp
> find . -name "*.el" -exec touch "{}" ";"
> make recompile
>
> Don't you see it?
I see this, but I also see the same thing with the emacs-24 branch.
(There, it is "Invalid byte code in cl-seq.elc".)
I don't think this is a new (or real) bug, it is just that `make
recompile' does the wrong thing (as was already known), since it
compiles everything in the same single Emacs instance.
As Stefan said in http://debbugs.gnu.org/11649#29
Usually "Invalid byte code in <foo>" happens because <foo> is
byte-compile-dynamic (as is the case for cl-macs) and you try to call
a function from it after byte-compiling a new version of the file.
More specifically, the scenario is:
1- load cl-macs.elc.
2- don't call function <bla>.
3- change cl-macs.elc.
4- call <bla> which is dynamically loaded from cl-macs.elc.
5- now the offset loaded at point 1 is not valid any more, so you get an
error: you need to re-load cl-macs.elc.
AFAICS, nobody is claiming that the "invalid byte code" happens buring
*bootstrap*, which would be a new, serious bug.
AFAICS, all the actual problems are fixed in this area (expect perhaps
MS Windows specific build efficiency issues).
next prev parent reply other threads:[~2012-06-14 17:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 13:19 bug#11649: Some compilation woes Juanma Barranquero
2012-06-09 9:29 ` bug#11649: 24.1.50; " Eli Zaretskii
2012-06-09 10:05 ` Juanma Barranquero
2012-06-09 11:41 ` Eli Zaretskii
2012-06-09 19:28 ` Juanma Barranquero
2012-06-10 2:52 ` Eli Zaretskii
2012-06-09 10:14 ` martin rudalics
2012-06-09 11:38 ` Eli Zaretskii
2012-06-09 13:02 ` martin rudalics
2012-06-10 1:08 ` Stefan Monnier
2012-06-10 2:59 ` Eli Zaretskii
2012-06-10 14:40 ` Stefan Monnier
2012-06-10 16:05 ` Eli Zaretskii
2012-06-13 14:12 ` Stefan Monnier
2012-06-13 15:35 ` Eli Zaretskii
2012-06-13 16:39 ` Stefan Monnier
2012-06-14 3:06 ` Eli Zaretskii
2012-06-14 3:32 ` Stefan Monnier
2012-06-14 17:10 ` Eli Zaretskii
2012-06-14 17:56 ` Glenn Morris [this message]
2012-06-14 18:27 ` Juanma Barranquero
2012-06-14 19:28 ` Eli Zaretskii
2012-06-15 17:45 ` Juanma Barranquero
2012-06-15 18:27 ` Eli Zaretskii
2012-06-15 19:22 ` Juanma Barranquero
2012-06-14 17:51 ` Glenn Morris
2012-06-12 21:35 ` Juanma Barranquero
2012-06-12 22:27 ` Glenn Morris
2012-06-12 22:39 ` Glenn Morris
2012-06-13 11:09 ` Juanma Barranquero
2012-06-13 12:56 ` Stefan Monnier
2012-06-15 3:19 ` Stefan Monnier
2012-06-13 12:48 ` Stefan Monnier
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=oiwr393hgm.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11649@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@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 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.