From: Johan Andersson <johan.rejeep@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15218@debbugs.gnu.org
Subject: bug#15218: End of file during parsing only for byte compiled files
Date: Sat, 31 Aug 2013 10:25:22 +0200 [thread overview]
Message-ID: <CAB6RKMtHT==hxVKFmX1Dx=P2mgnqW3t8rh2JQ9ARinuvSicbRQ@mail.gmail.com> (raw)
In-Reply-To: <CAB6RKMtgQq24vVJLntLN4zPx-0Gt6FH-53W0qZpvGf1YS+HVPQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
This might have to do with that the package advices `princ', which seems to
be used in the byte compilation process. I've pushed a fix and waiting for
MELPA before I can verify this.
On Fri, Aug 30, 2013 at 5:10 PM, Johan Andersson <johan.rejeep@gmail.com>wrote:
> > I'm not sure when you see that error (is it when loading the package or
> when installing it?).
>
> Loading, yes!
>
> > Assuming it's when loading it, could it be that
> you're loading the package in a version of Emacs noticeably older than
> the one that compiled the files?
>
> No, it's the exact same binary that installed the package as the one
> running it. But if I look at the byte code, the one that package.el
> produced is not the same as if I would run byte-compile-file.
>
> > The elpa package is supposed to come without any .elc files, and the .el
> files are supposed to be byte-compiled during installation. Did this
> work correctly?
>
> I can see no errors or warnings. See attached log file.
>
>
> On Fri, Aug 30, 2013 at 2:36 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
>
>> > I just released a new version of Ecukes (
>> https://github.com/rejeep/ecukes.el).
>> > Everything works fine locally, but not when I install via package.el.
>> Then
>> > I get this error:
>>
>> > End of file during parsing:
>> > /path/to/project/.cask/24.3.1/elpa/ecukes-20130830.16/ecukes-core.elc
>>
>> > And if I remove that .elc file, it complains on the next file and so
>> on. If
>> > I remove all .elc files it works fine.
>>
>> I'm not sure when you see that error (is it when loading the package or
>> when installing it?). Assuming it's when loading it, could it be that
>> you're loading the package in a version of Emacs noticeably older than
>> the one that compiled the files?
>>
>> > So something with the byte compilation does not work, but if I byte
>> compile
>> > all files locally it works just fine.
>>
>> The elpa package is supposed to come without any .elc files, and the .el
>> files are supposed to be byte-compiled during installation. Did this
>> work correctly?
>>
>>
>> Stefan
>>
>
>
[-- Attachment #2: Type: text/html, Size: 3306 bytes --]
next prev parent reply other threads:[~2013-08-31 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 8:13 bug#15218: End of file during parsing only for byte compiled files Johan Andersson
2013-08-30 12:36 ` Stefan Monnier
2013-08-30 15:10 ` Johan Andersson
2013-08-31 8:25 ` Johan Andersson [this message]
2013-09-03 19:03 ` Stefan Monnier
2013-09-03 19:26 ` Johan Andersson
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='CAB6RKMtHT==hxVKFmX1Dx=P2mgnqW3t8rh2JQ9ARinuvSicbRQ@mail.gmail.com' \
--to=johan.rejeep@gmail.com \
--cc=15218@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).