From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Prickliness of the "invalid byte code" stuff
Date: Sat, 15 Jun 2019 16:30:07 +0200 [thread overview]
Message-ID: <87tvcq9b0w.fsf@igel.home> (raw)
In-Reply-To: <m34l4rkoti.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 15 Jun 2019 14:36:41 +0200")
On Jun 15 2019, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> One thing that I've always wondered about when building Emacs is that
> running Emacs instances then start to fail in odd ways:
>
> url-http-parse-headers: Invalid byte code in /home/larsi/src/emacs/trunk/lisp/emacs-lisp/cl-seq.elc [8 times]
>
> And it's almost always with this "invalid byte code" stuff.
>
> What does it mean, really?
emacs-lisp/cl-seq.elc was modified after being loaded. You need to
reload it.
> Is there some sanity check to ensure that you're not running an .elc
> file designed for a different Emacs build, or... something else?
See byte-compile-dynamic.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-06-15 14:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 12:36 Prickliness of the "invalid byte code" stuff Lars Ingebrigtsen
2019-06-15 14:30 ` Andreas Schwab [this message]
2019-06-16 2:40 ` Richard Stallman
2019-06-16 12:41 ` Lars Ingebrigtsen
2019-06-16 13:27 ` Stefan Monnier
2019-06-16 17:47 ` T.V Raman
2019-06-16 22:01 ` Stefan Monnier
2019-06-17 2:39 ` T.V Raman
2019-06-17 13:32 ` Stefan Monnier
2019-06-17 16:04 ` Richard Stallman
2019-06-17 18:10 ` Stefan Monnier
2019-06-17 22:52 ` Paul Eggert
2019-06-17 22:53 ` Stefan Monnier
2019-06-18 0:14 ` T.V Raman
2019-06-18 12:14 ` Stefan Monnier
2019-06-18 13:51 ` T.V Raman
2019-06-18 14:15 ` T.V Raman
2019-06-18 16:31 ` Eli Zaretskii
2019-06-18 18:11 ` Stefan Monnier
2019-06-18 18:23 ` T.V Raman
2019-06-18 18:52 ` Eli Zaretskii
2019-06-18 19:54 ` T.V Raman
2019-06-19 2:36 ` Eli Zaretskii
2019-06-19 13:54 ` T.V Raman
2019-06-19 15:36 ` Eli Zaretskii
2019-06-18 18:44 ` Eli Zaretskii
2019-06-18 19:48 ` Stefan Monnier
2019-06-18 19:52 ` Stefan Monnier
2019-06-19 16:08 ` Eli Zaretskii
2019-06-19 16:25 ` Stefan Monnier
2019-06-19 17:04 ` Eli Zaretskii
2019-06-19 19:02 ` Stefan Monnier
2019-06-19 21:35 ` T.V Raman
2019-06-21 7:52 ` Eli Zaretskii
2019-06-21 14:10 ` T.V Raman
2019-06-21 14:15 ` Eli Zaretskii
2019-06-21 14:34 ` Stefan Monnier
2019-06-21 15:04 ` Eli Zaretskii
2019-06-18 3:09 ` Richard Stallman
2019-06-17 16:01 ` 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=87tvcq9b0w.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.