From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: emacs-guix invalid byte opcode: op=183 ptr=25
Date: Thu, 28 Feb 2019 20:03:46 +0100 [thread overview]
Message-ID: <8736o7zqel.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ2CC5c__BC6Tbz858wrrWvXXZgHf_DZfK6O=e2AdbWMuw@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> I am confused and I have a really naive question. :-)
>
> When `guix package -i emacs-stuff', well the `emacs-stuff` is built or
> if it is available on a substitute then the package is pulled from
> there.
> So,
> a- does it pull the ".el" files and then byte-compile them locally?
> Or b- does it pull the ".elc" byte-compiled on the substitute?
The files are byte-compiled as part of the build process, so the elc
files are part of the substitute.
--
Ricardo
prev parent reply other threads:[~2019-02-28 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:28 emacs-guix invalid byte opcode: op=183 ptr=25 Yoshinori Arai
2019-02-28 10:37 ` Pierre Neidhardt
2019-02-28 12:26 ` zimoun
2019-02-28 13:28 ` Pierre Neidhardt
2019-02-28 14:47 ` emacs byte-compiled packages incompatibilities (was Re: emacs-guix invalid byte opcode: op=183 ptr=25) Giovanni Biscuolo
2019-02-28 15:11 ` Pierre Neidhardt
2019-02-28 19:03 ` Ricardo Wurmus [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736o7zqel.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).