From: zamfofex <zamfofex@twdb.moe>
To: "54832@debbugs.gnu.org" <54832@debbugs.gnu.org>
Cc: "maximedevos@telenet.be" <maximedevos@telenet.be>
Subject: [bug#54832] Fwd: Re: [bug#54832] [patch] update glibc to 2.35
Date: Sun, 24 Apr 2022 11:19:26 -0300 (BRT) [thread overview]
Message-ID: <600444931.762626.1650809966586@privateemail.com> (raw)
In-Reply-To: <1497835452.18920.1649591936889@privateemail.com>
> Why are empty static libraries skipped? Would "gcc -static -lpthread main.c" (*)
> (in an environment that includes glibc:static) still work, or does it now fail?
They are skipped from being moved, but then should be copied in the loop immediately below it.
> An explanation and a link to an upstream report is mising.
> (apparently upstream=Guix here?).
I’m not sure if there is a report yet. There is a conversation in IRC, however. See:
- <https://logs.guix.gnu.org/guix/2022-04-09.log#081848>
- <https://logs.guix.gnu.org/guix/2022-04-09.log#082442>
- <https://logs.guix.gnu.org/guix/2022-04-09.log#171259>
- <https://logs.guix.gnu.org/guix/2022-04-09.log#174339>
> What's the reason for this patch?
‘/bin/sh’ doesn’t seem available in the build environment, so tests were failing. From what I was able to see, that macro is only used in tests, so I didn’t think it would be worthwhile to make it refer to ‘/gnu/store/.../bash’.
- - - - - - -
Apologies to Maxime for the repeated messages, and to others for taking so long to reply. Apparently I hadn’t replied to the debbugs address, so my initial messages were sent only to Maxime.
I hope this can be looked into soon enough!
next prev parent reply other threads:[~2022-04-24 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 1:16 [bug#54832] [patch] update glibc to 2.35 zamfofex
2022-04-10 10:16 ` Maxime Devos
[not found] ` <1497835452.18920.1649591936889@privateemail.com>
2022-04-24 14:19 ` zamfofex [this message]
2022-04-10 10:17 ` Maxime Devos
2022-04-10 10:18 ` Maxime Devos
2022-05-15 21:31 ` Ludovic Courtès
2022-06-06 12:06 ` zamfofex
2022-07-17 10:06 ` Ludovic Courtès
2022-07-19 14:12 ` zamfofex
2022-07-19 19:16 ` Greg Hogan
2022-09-01 22:32 ` bug#54832: " Marius Bakke
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=600444931.762626.1650809966586@privateemail.com \
--to=zamfofex@twdb.moe \
--cc=54832@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).