From: Tassilo Horn <tassilo@member.fsf.org>
To: Pierre Lorenzon <devel@pollock-nageoire.net>
Cc: help-gnu-emacs@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Corrupted byte compiled files
Date: Thu, 31 May 2012 13:43:39 +0200 [thread overview]
Message-ID: <8762bc7ez8.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <20120530.085415.424292590.devel@pollock-nageoire.net> (Pierre Lorenzon's message of "Wed, 30 May 2012 08:54:15 +0200 (CEST)")
Pierre Lorenzon <devel@pollock-nageoire.net> writes:
> From: Stefan Monnier <monnier@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
next prev parent reply other threads:[~2012-05-31 11:43 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 [this message]
[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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762bc7ez8.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=devel@pollock-nageoire.net \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.