From: Hilton Chain via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Brian Cully <bjc@spork.org>
Cc: 65461@debbugs.gnu.org, Josselin Poiret <dev@jpoiret.xyz>,
Jonas <jonas@moesys.no>
Subject: bug#65461: Cannot compile any Rust projects
Date: Thu, 24 Aug 2023 10:08:32 +0800 [thread overview]
Message-ID: <87o7ixur8f.wl-hako@ultrarare.space> (raw)
In-Reply-To: <87zg2hbovk.fsf@spork.org>
Hello Brian,
On Thu, 24 Aug 2023 02:22:07 +0800,
brian wrote:
>
> I'd like to propose that the ‘out’ output of gcc-toolchain include the
> stub rt, pthread, and dl stub static libraries. This problem comes up on
> a very regular basis, and I can think of no reason not to have the
> compatibility shims made available.
>
> They contain no code, as they only exist to satisfy linker command
> lines, so they're not relevant for grafting purposes. The workaround of
> including the static toolchain means that every static library, not just
> the empty stubs, is made availible for linking, which is, IMHO, strictly
> worse than putting empty .a files into the default output.
>
> WDYT?
Grepping "!<arch>" in gcc-toolchain:static gives me libanl.a, libdl.a,
libpthread.a, librt.a and libutil.a. Currently only librt.a is not
present in gcc-toolchain:out, so the proposal is really reasonable for
me.
Cc-ing Josselin since they have sent a patch to #63258.
Hi Josselin, what's the current state of the patch? Can you resend it
to guix-patches to trigger the build process?
Thanks
next prev parent reply other threads:[~2023-08-24 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 22:59 bug#65461: Cannot compile any Rust projects Jonas via Bug reports for GNU Guix
2023-08-23 3:36 ` Hilton Chain via Bug reports for GNU Guix
2023-08-23 18:22 ` brian via Bug reports for GNU Guix
2023-08-24 2:08 ` Hilton Chain via Bug reports for GNU Guix [this message]
2023-08-25 11:03 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 16:37 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 12:58 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 13:30 ` Jonas Møller via Bug reports for GNU Guix
2023-08-29 21:03 ` Maxim Cournoyer
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=87o7ixur8f.wl-hako@ultrarare.space \
--to=bug-guix@gnu.org \
--cc=65461@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=dev@jpoiret.xyz \
--cc=hako@ultrarare.space \
--cc=jonas@moesys.no \
/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).