From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>,
John Kehayias <john.kehayias@protonmail.com>
Cc: Christopher Rodriguez <yewscion@gmail.com>,
63267@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: gcc-toolchain is missing libstdc++.so
Date: Thu, 4 May 2023 12:14:40 -0600 [thread overview]
Message-ID: <0011bd8c-d32f-bb4b-d1d9-f6539ce20fe9@gmail.com> (raw)
In-Reply-To: <NxF4Z9svIqfZ4ZdSP_LlErXklwpO8siFWZ_aY-KAjK6bfBJ-5xhHJqziFO0pxyQBM4Y79IkCGewvY3Q_2AZETfJ3Rwzrod3OFSwOvm7qov0=@protonmail.com>
On 5/4/23 11:33 AM, Kaelyn wrote:
> Regarding solutions, I would prefer to have libstdc++ in it's own package or output rather than bundled into gcc-toolchain:out; it feels messy and against the grain of isolating programs in containers if I have to make the gcc and g++ compilers available in the container in order to run a program that needs libstdc++.
+1. I recently ran into this as well and went looking for it.
I think a good reason to give libstdc++ its own output is that this
question continually gets asked.
--
Katherine
next prev parent reply other threads:[~2023-05-04 18:15 UTC|newest]
Thread overview: 14+ 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:05 ` Christopher Rodriguez
2023-05-04 15:26 ` bug#63267: " John Kehayias via Bug reports for GNU Guix
2023-05-04 17:33 ` Kaelyn
2023-05-04 18:14 ` Katherine Cox-Buday [this message]
2023-05-04 15:23 ` bug#63267: Possible Solution Christopher Rodriguez
2023-05-04 17:34 ` bug#63267: gcc-toolchain is missing libstdc++.so 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
2024-04-22 0:14 ` Simon Tournier
-- strict thread matches above, loose matches on Subject: below --
2023-05-04 21:50 John Kehayias
2023-05-04 23:45 ` Kaelyn
2023-05-05 20:59 ` John Kehayias
2023-05-05 23:59 ` Kaelyn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0011bd8c-d32f-bb4b-d1d9-f6539ce20fe9@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=63267@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=kaelyn.alexi@protonmail.com \
--cc=yewscion@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.