From: Pierre Lorenzon <devel@pollock-nageoire.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Corrupted byte compiled files
Date: Fri, 01 Jun 2012 08:51:58 +0200 (CEST) [thread overview]
Message-ID: <20120601.085158.466698019.devel@pollock-nageoire.net> (raw)
In-Reply-To: <87ipfc9rc7.fsf@gnu.org>
Hi,
From: Johan Bockgård <bojohan+news@gnu.org>
Subject: Re: Corrupted byte compiled files
Date: Thu, 31 May 2012 19:46:00 +0200
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Argh, some very recent change in trunk seems to have hosed
>> byte-compilation altogether for me. I have several emacs addon packages
>> like Gnus, AUCTeX, helm cloned from their repositories, and as soon as I
>> byte-compile those with today's emacs (revno 108437), they won't work at
>> all. It seems there are complete functions missing in the elc files and
>> I get dozens of "Wrong type argument" errors at different locations.
>> After deleting all elc files and running from the plain elisp sources,
>> everything works again.
I think that the problem is different from mine. Indeed the
compilation problem I encountered was due to the
byte-compile-fix-header method which was clearly bugged. But
we solved that.
Pierre
>
> Probably the same as
>
> http://debbugs.gnu.org/11594
next prev parent reply other threads:[~2012-06-01 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1848.1338298974.855.help-gnu-emacs@gnu.org>
2012-05-29 18:39 ` Corrupted byte compiled files Stefan Monnier
2012-05-30 6:54 ` Pierre Lorenzon
2012-05-31 11:43 ` Tassilo Horn
[not found] ` <mailman.2011.1338480750.855.help-gnu-emacs@gnu.org>
2012-05-31 17:46 ` Johan Bockgård
2012-05-31 18:56 ` Tassilo Horn
2012-06-01 6:51 ` Pierre Lorenzon [this message]
2012-05-29 13:25 Pierre Lorenzon
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=20120601.085158.466698019.devel@pollock-nageoire.net \
--to=devel@pollock-nageoire.net \
--cc=help-gnu-emacs@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.
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).