From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42339@debbugs.gnu.org
Subject: [bug#42339] [PATCH core-updates] gnu: glibc-intermediate: Fixup the pre-configure phase.
Date: Thu, 23 Jul 2020 00:37:21 +0200 [thread overview]
Message-ID: <20200722223721.upm7cf2gnghfv2pp@gravity> (raw)
In-Reply-To: <874kpzgqh5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
On Thu, Jul 23, 2020 at 12:00:22AM +0200, Ludovic Courtès wrote:
> Hello,
>
> Jakub Kądziołka <kuba@kadziolka.net> skribis:
>
> > * gnu/packages/commencement.scm
> > (glibc-final-with-bootstrap-bash)[arguments]: Don't patch sunrpc,
> > as it's no longer required. Tweak C_INCLUDE_PATH and
> > CPLUS_INCLUDE_PATH instead of CPATH.
> > ---
> >
> > Hi Guix,
> >
> > I have stumbled upon this phase while I was working on making substitute
> > not fail silently. Turns out this substitution is no longer necessary
> > since we aren't building with --enable-obsolete-rpc anymore. I'm not
> > sure about the unsetenv parts, though. Switching them to
> > {C,CPLUS}_INCLUDE_PATH, which is where the header paths actually are
> > right now, did not change how `guix graph --type=references` looks for
> > glibc-final (nor glibc-final-with-bootstrap-bash, for that matter).
> >
> > The phase itself was introduced in...
> >
> > commit 1c93be5600fb90a64cbbdf7a55061902d2ff150a
> > Author: Ludovic Courtès <ludo@gnu.org>
> > Date: Sat Jun 7 17:23:53 2014 +0200
> >
> > gnu: glibc: Make sure the bootstrap libc is not in $CPATH.
> >
> > This fixes a bug whereby the bootstrap-glibc headers could be picked up
> > when building libc.so, which could be noticed by the fact that the
> > .debug files contained references to bootstrap-glibc.
> >
> > * gnu/packages/base.scm (glibc-final-with-bootstrap-bash)[arguments]:
> > Add 'pre-configure' phase.
> > [inputs]: Remove 'alist-delete' call.
> >
> > The debug output does not refer to a bootstrap glibc anymore whether the phase
> > is there or not, though it does refer to gcc-cross-boot0:lib. Does this
> > mean that the phase is simply obsolete, and only the hurd parts should
> > remain, or is the reference to gcc a bug? Perhaps gcc should have a
> > separate output for the includes it provides (stdarg and such) so that
> > this reference doesn't bring in the whole mesboot tree? This would
> > improve the closure of gcc-toolchain:debug...
>
> Oooh, nice. LGTM!
Thanks for your review!
> Please confirm that nothing breaks (everything builds at least up to
> ‘gcc-final’) and you can push to ‘core-updates’.
I have confirmed that hello builds both natively and cross-built. On a
similar topic, the same test succeeded for removing the native-gcc input.
As the comment suggests, it was only being used for --enable-obsolete-rpc.
I am thus considering a v2 that also removes said input. Does that make
sense?
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-22 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 23:40 [bug#42339] [PATCH core-updates] gnu: glibc-intermediate: Fixup the pre-configure phase Jakub Kądziołka
2020-07-22 22:00 ` Ludovic Courtès
2020-07-22 22:37 ` Jakub Kądziołka [this message]
2020-07-23 7:49 ` Ludovic Courtès
2020-07-23 22:15 ` bug#42339: " Jakub Kądziołka
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=20200722223721.upm7cf2gnghfv2pp@gravity \
--to=kuba@kadziolka.net \
--cc=42339@debbugs.gnu.org \
--cc=ludo@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).