From: Julien Lepiller <julien@lepiller.eu>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56051-done@debbugs.gnu.org
Subject: bug#56051: [PATCH] guix: self: Do not record reference to gcc-toolchain.
Date: Sat, 18 Jun 2022 22:14:01 +0200 [thread overview]
Message-ID: <20220618221401.681618e0@sybil.lepiller.eu> (raw)
In-Reply-To: <d194103126abdff55d8e4dc6731686e76ff26d21.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Le Sat, 18 Jun 2022 21:08:18 +0200,
Maxime Devos <maximedevos@telenet.be> a écrit :
> Julien Lepiller schreef op za 18-06-2022 om 19:53 [+0200]:
> > crt1.o and friends, from glibc. I tried using glibc explicitely and
> > setting LIBRARY_PATH to (file-append glibc "/lib") and it worked.
> >
> > >
> > > > Another possibility is to explicitely use gcc, binutils, glibc
> > > > and ld-wrapper. Thought this would be better?
> > >
> > > FWIW, the <c-compiler> infrastructure in (guix scripts pack) does
> > > that, and the code in guix/self.scm has a comment:
> > >
> > > ;; XXX: Reuse <c-compiler> from (guix scripts pack) instead?
> > >
> > > though maybe (guix scripts pack) has the same reference-keeping
> > > problem ...
> > >
> > > Greetings,
> > > Maxime.
> >
> > Mh, I'm not sure how to do that. Do you mind if I push this patch,
> > and leave using <c-compiler> to future work?
>
> Sure, but keep in mind this adds 'glibc' to the closure (IIUC,
> packages like 'hello' use a different glibc, from %final-inputs in
> (gnu packages commencement)), so maybe best use (canonical-package
> glibc) instead? (*)
>
> (*) IIUC, (guix self) isn't used from any package module, so no cycle
> problems, can be imported directly.
>
> Greetings,
> Maxime
I didn't notice a different glibc. I think gcc-toolchain already uses
that glibc from commencement.scm. It's also defined in commencement.scm.
Pushed to master as 319b8331b2357e12ec9edb9665513c32bef56622.
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-18 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 6:46 [bug#56051] Julien Lepiller
2022-06-18 6:58 ` [bug#56051] [PATCH] guix: self: Do not record reference to gcc-toolchain Julien Lepiller
2022-06-18 9:45 ` Maxime Devos
2022-06-18 12:13 ` Julien Lepiller
2022-06-18 17:23 ` Maxime Devos
2022-06-18 17:53 ` Julien Lepiller
2022-06-18 19:08 ` Maxime Devos
2022-06-18 20:14 ` Julien Lepiller [this message]
2022-06-18 20:20 ` Maxime Devos
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=20220618221401.681618e0@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=56051-done@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).