Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Corrupted byte compiled files

11 views
Skip to first unread message

Stefan Monnier

unread,
May 29, 2012, 2:39:09 PM5/29/12
to
> Certain of my .el files are incorrectly compiled. See the .elc
> file with a long name.

Indeed, I can reproduce it here, and also with Emacs-23.
I don't have time to dig into it now, tho, so please M-x
report-emacs-bug so it doesn't get lost.


Stefan

Pierre Lorenzon

unread,
May 30, 2012, 2:54:15 AM5/30/12
to help-gn...@gnu.org
From: Stefan Monnier <mon...@iro.umontreal.ca>
Subject: Re: Corrupted byte compiled files
Date: Tue, 29 May 2012 14:39:09 -0400

>> Certain of my .el files are incorrectly compiled. See the .elc
>> file with a long name.
>
> Indeed, I can reproduce it here, and also with Emacs-23.

Does that mean that none never tried to compile file with
long name before .... or that the problem does not come
exclusively from the length of the name ....



> I don't have time to dig into it now, tho, so please M-x
> report-emacs-bug so it doesn't get lost.

OK I'll do that. But since I now know that there is really a
problem I'll have a look at the byte compiling engine
code. Maybe I can discover where is th problem ....


Thanks

Pierre



>
>
> Stefan

Tassilo Horn

unread,
May 31, 2012, 7:43:39 AM5/31/12
to Pierre Lorenzon, help-gn...@gnu.org, Stefan Monnier
Pierre Lorenzon <de...@pollock-nageoire.net> writes:

> From: Stefan Monnier <mon...@iro.umontreal.ca>
> Subject: Re: Corrupted byte compiled files
> Date: Tue, 29 May 2012 14:39:09 -0400
>
>>> Certain of my .el files are incorrectly compiled. See the .elc
>>> file with a long name.
>>
>> Indeed, I can reproduce it here, and also with Emacs-23.
>
> Does that mean that none never tried to compile file with
> long name before .... or that the problem does not come
> exclusively from the length of the name ....

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.

Bye,
Tassilo

Johan Bockgård

unread,
May 31, 2012, 1:46:00 PM5/31/12
to
Tassilo Horn <tas...@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.

Probably the same as

http://debbugs.gnu.org/11594

Tassilo Horn

unread,
May 31, 2012, 2:56:26 PM5/31/12
to help-gn...@gnu.org
Yes, those are the same symptoms I have here. Thanks for the pointer.

Bye,
Tassilo


Pierre Lorenzon

unread,
Jun 1, 2012, 2:51:58 AM6/1/12
to help-gn...@gnu.org

Hi,


From: Johan Bockgård <bojoha...@gnu.org>
Subject: Re: Corrupted byte compiled files
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
0 new messages