From: Julien Lepiller <julien@lepiller.eu>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56051@debbugs.gnu.org
Subject: [bug#56051] [PATCH] guix: self: Do not record reference to gcc-toolchain.
Date: Sat, 18 Jun 2022 19:53:25 +0200 [thread overview]
Message-ID: <20220618195319.3b9af9b9@sybil.lepiller.eu> (raw)
In-Reply-To: <ac7073aa50b23159e9c9afc25045a77c060a40b8.camel@telenet.be>
Le Sat, 18 Jun 2022 19:23:28 +0200,
Maxime Devos <maximedevos@telenet.be> a écrit :
> Julien Lepiller schreef op za 18-06-2022 om 14:13 [+0200]:
> > On June 18, 2022 11:45:43 AM GMT+02:00, Maxime Devos
> > <maximedevos@telenet.be> wrote:
> > > Julien Lepiller schreef op za 18-06-2022 om 08:58 [+0200]:
> > > > (setenv "LIBRARY_PATH" #$(file-append gcc "/lib"))
> > >
> > > I'm wondering if is this line that is incorrect, given that the
> > > 'gcc:out' store item does not have a /lib subdirectory. Would
> > > removing this line be sufficient?
> > >
> > > Greetings,
> > > Maxime.
> >
> > Removing this line I get a message that gcc can't find crt*.o.
>
> Which crt are these? crt1.o, crti.o, crtn.o (from glibc) or
> crtbegin.o, crtend.o, crtprec64.o, ... (from gcc)?
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?
next prev parent reply other threads:[~2022-06-18 17:54 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 [this message]
2022-06-18 19:08 ` Maxime Devos
2022-06-18 20:14 ` bug#56051: " Julien Lepiller
2022-06-18 20:20 ` [bug#56051] " 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=20220618195319.3b9af9b9@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=56051@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).