From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Adam Porter <adam@alphapapa.net>, 64999@debbugs.gnu.org
Subject: bug#64999: Acknowledgement (emacs-next: emacs-29.1 fails to native-compile libraries, giving a runtime error that ctri.o and other files can't be found)
Date: Sun, 06 Aug 2023 10:10:10 +0200 [thread overview]
Message-ID: <87pm40egm5.fsf@jpoiret.xyz> (raw)
In-Reply-To: <2c7fd0d0-0682-5984-8e09-67088ef6c94f@alphapapa.net>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Hi Adam,
Adam Porter <adam@alphapapa.net> writes:
> OTOH, if anyone knows why the transformation option failed in that way,
> it might be helpful to solve it if possible, so users could use the
> option to install future releases without having to modify the package
> definition. (AFAIK, I was able to do that for various Emacs 28 versions
> without this problem, so I wonder if something's changed.)
It's probably because emacs is missing the
emacs-native-comp-driver-options.patch patch of emacs-next. Package
transformations can't and won't replace the manual work of packaging new
versions, so I think it is unreasonable to expect emacs 28's package
definition to work with emacs 29.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-08-06 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:00 bug#64999: emacs-next: emacs-29.1 fails to native-compile libraries, giving a runtime error that ctri.o and other files can't be found Adam Porter
[not found] ` <handler.64999.B.169091282922666.ack@debbugs.gnu.org>
2023-08-01 22:37 ` bug#64999: Acknowledgement (emacs-next: emacs-29.1 fails to native-compile libraries, giving a runtime error that ctri.o and other files can't be found) Adam Porter
2023-08-06 8:10 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-08-23 16:26 ` Simon Tournier
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=87pm40egm5.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=64999@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=dev@jpoiret.xyz \
/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/guix.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).