unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: 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: Tue, 1 Aug 2023 17:37:30 -0500	[thread overview]
Message-ID: <2c7fd0d0-0682-5984-8e09-67088ef6c94f@alphapapa.net> (raw)
In-Reply-To: <handler.64999.B.169091282922666.ack@debbugs.gnu.org>

FYI, I hacked together a new package definition, updating the emacs-next 
one to build 29.1 from the release tarball, and after installing it, 
everything seems to work, including native compilation.

I don't know enough about Guix to understand why using "guix install" 
with the package transformation option caused the runtime problem with 
gcc, but everything does seem to work with the updated definition.

So I guess this report can be closed.

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.)

See also: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65000




  parent reply	other threads:[~2023-08-04 20: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   ` Adam Porter [this message]
2023-08-06  8:10     ` 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) Josselin Poiret via Bug reports for GNU Guix
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=2c7fd0d0-0682-5984-8e09-67088ef6c94f@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=64999@debbugs.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 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).