From: Bhavin Gandhi <bhavin7392@gmail.com>
To: emacs-devel@gnu.org
Subject: Packaging Emacs with native compilation enabled
Date: Sun, 5 Dec 2021 19:02:08 +0530 [thread overview]
Message-ID: <CAOn=hbfPOrqkWg06Fkp8-_XBDerM_k+C3VViNhh4CBuuFBqLfQ@mail.gmail.com> (raw)
This is the first time I'm creating a new thread on this list. Sorry, if
this is not the correct place to discuss this.
I'm packaging the 28.0.90 pretest as RPM with native compilation
enabled. The `make install' installs some .eln files to lib64 directory
i.e. /usr/lib64/emacs/28.0.90/native-lisp/28.0.90-<hash>/.
1. Should these files be there in the final package, which is
distributed to users?
Based on what I have understood from Andrea's EmacsConf 2021 talk[1] and
the "(elisp) Native Compilation" page: the .eln files are CPU specific
and should not be shared across. And those will be created when Emacs
starts on the end user's machine.
With that in mind, I deleted the *.eln files from the package. But when
I start emacs-nox (the one without X), it gives this error:
$ emacs-nox -Q
Error using execdir /usr/bin/:
emacs: /usr/bin/../native-lisp/28.0.90-f21cc02e/preloaded/frame-b40fc590-e67d4a02.eln:
cannot open shared object file: No such file or directory
If I add the 28.0.90-f21cc02e directory to the lib64 directory
mentioned above, it starts correctly. I can see the path in
`native-comp-eln-load-path' variable.
I think those .eln files are required. If so, is it okay to package and
distribute these .eln files along with the emacs binary?
If this is already discussed / documented somewhere, can anyone please
point me to that resource?
[1] https://emacsconf.org/2021/talks/native/
--
Regards,
Bhavin Gandhi (bhavin192) | https://geeksocket.in
next reply other threads:[~2021-12-05 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 13:32 Bhavin Gandhi [this message]
2021-12-05 14:00 ` Packaging Emacs with native compilation enabled Eli Zaretskii
2021-12-05 18:20 ` Bhavin Gandhi
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='CAOn=hbfPOrqkWg06Fkp8-_XBDerM_k+C3VViNhh4CBuuFBqLfQ@mail.gmail.com' \
--to=bhavin7392@gmail.com \
--cc=emacs-devel@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.
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.