From: John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, cox.katherine.e@gmail.com,
Christopher Rodriguez <yewscion@gmail.com>,
kaelyn.alexi@protonmail.com, 63267-done@debbugs.gnu.org
Subject: bug#63267: gcc-toolchain is missing libstdc++.so
Date: Wed, 17 Apr 2024 05:21:25 +0000 [thread overview]
Message-ID: <8734rk36pb.fsf@protonmail.com> (raw)
In-Reply-To: <871qjp5t84.fsf@gmail.com>
Hi everyone,
Apologies for the long delay on this.
On Tue, May 09, 2023 at 07:07 PM, Simon Tournier wrote:
> Hi,
>
> I am proposing patch#63393 [1] which adds the output lib to
> gcc-toolchain. Well, quoting the comment:
>
> ;; The main raison d'être of this "meta-package" is (1) to conveniently
> ;; install everything that we need, and (2) to make sure ld-wrapper comes
> ;; before Binutils' ld in the user's profile.
>
> I think, this package gcc-toolchain should be the visible package and
> battery included.
>
> WDYT?
>
> 1: https://issues.guix.gnu.org/issue/63393
>
> Cheers,
> simon
I've just pushed, as b47ae1ecc43baaf726701ab2d2f810ecfaa75428, the
patches from that issue (the first from simon, the second my simplified
one just adding gcc:lib to gcc-toolchain).
This should fix the original bug here, so I am closing. However, it was
raised here and in 63393 about alternatives in how we use gcc-toolchain
outputs. As well as the issue I ran into about make-libstdc++.
So, if anyone would like to change anything from the new status quo,
please open a new issue. At least now we are working from a better
default I would say, with gcc-toolchain including the libraries from
gcc:lib.
Thanks all,
John
next prev parent reply other threads:[~2024-04-17 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 14:46 gcc-toolchain is missing libstdc++.so Christopher Rodriguez
2023-05-04 15:23 ` bug#63267: Possible Solution Christopher Rodriguez
[not found] ` <pkmp4eild8m8z9.fsf@u6908d19b746052.ant.amazon.com>
2023-05-04 15:26 ` bug#63267: gcc-toolchain is missing libstdc++.so John Kehayias via Bug reports for GNU Guix
2023-05-04 17:34 ` John Kehayias via Bug reports for GNU Guix
2023-05-09 17:07 ` Simon Tournier
2024-04-17 5:21 ` John Kehayias via Bug reports for GNU Guix [this message]
[not found] <87sfcbzrzy.fsf@protonmail.com>
[not found] ` <Ep1v1JJOnsfi7wG0QvKyBwOVsowFkmpd4B5orgUDEHZzshS6Xnb_nKaokIlcDbD18XvH4n9DVajid9RPnkd_95UtHfMnYRzR57sj6KadoKw=@protonmail.com>
[not found] ` <87h6sqze9d.fsf@protonmail.com>
[not found] ` <1pOI6MV7sx3-zolxwH99rQ93RMcbp677fn9twoyv4ZhNBhicZgnNC4bI_u0-aJCfLOjBDb_q8wmu_JihwNW7ECzh-RUmTn3c4jwfd2BCz-4=@protonmail.com>
2023-05-08 8:41 ` Josselin Poiret via Bug reports for GNU Guix
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=8734rk36pb.fsf@protonmail.com \
--to=bug-guix@gnu.org \
--cc=63267-done@debbugs.gnu.org \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=kaelyn.alexi@protonmail.com \
--cc=yewscion@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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).