From: Kaelyn <kaelyn.alexi@protonmail.com>
To: 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, 04 May 2023 17:33:42 +0000 [thread overview]
Message-ID: <NxF4Z9svIqfZ4ZdSP_LlErXklwpO8siFWZ_aY-KAjK6bfBJ-5xhHJqziFO0pxyQBM4Y79IkCGewvY3Q_2AZETfJ3Rwzrod3OFSwOvm7qov0=@protonmail.com> (raw)
In-Reply-To: <874jos15kh.fsf@protonmail.com>
Hi,
------- Original Message -------
On Thursday, May 4th, 2023 at 3:26 PM, John Kehayias <john.kehayias@protonmail.com> wrote:
>
> Hi Christopher,
>
> On Thu, May 04, 2023 at 11:05 AM, Christopher Rodriguez wrote:
>
> > Sorry for the spam; Resending this without the bugs address, but with
> > the issue's address.
> >
> > Christopher Rodriguez yewscion@gmail.com writes:
> >
> > > Hello All,
> > >
> > > I noticed today that libstdc++.so.1 (and some others), which used to be
> > > part of gcc:lib, are not included in any of the outputs of the
> > > superceding `gcc-toolchain` package.
> > >
> > > Is there another method for getting these needed shared libraries in a
> > > guix system at this point? It's entirely possible I'm missing something.
> > >
> > > I am CCing guix-devel@gnu.org per podiki[m]'s request.
> > >
> > > Thanks!
>
>
> Thanks for opening this and cc'ing; this has come up with some
> frequency on IRC, especially recently. In discussing there today, the
> current reasoning is that usually one will just call g++ which knows
> how to find libstdc++. So, gcc-toolchain does not include gcc:lib as
> part of what it makes available.
>
> I think what we (and when this comes up, others) are getting at are
> some edge cases or different use cases where one wants to directly get
> at libstdc++. Previously it was more direct to use gcc:lib; of course
> one still can in code and/or cli with the proper call. For example,
> guix build -e "(@@ (gnu packages gcc) gcc)" will download/build/show
> the lib output of the (hidden) gcc package. Though I'm not sure how to
> select just the lib output here.
>
> My use case currently is in the FHS container where a binary wants to
> find some libraries directly. Previously one would include the gcc:lib
> package output in the guix shell call. Now some of those libraries can
> be found elsewhere, like libgccjit, but libstdc++ seems to be the
> trickier one. Open to other suggestions/workarounds, or thoughts on if
> it is worthwhile to include gcc:lib in the gcc-toolchain package (or
> make a gcc-toolchain:lib output?).
I have similar use cases of FHS containers to run binaries (primarily games). I recently ran into the issue of gcc:lib going away and no output from a visible package providing libstdc++. My current workaround was to implement a replacement for specifications->manifest that could handle packages and '(package "output") pairs in addition to strings, so that I could include `(,(@@ (gnu packages gcc) gcc) "lib") in place of "gcc:lib". Internally it resolves package strings to packages with specification->package, then passes the package and optional output specifier to package->manifest-entry. But I digress a little...
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++.
Cheers,
Kaelyn
next prev parent reply other threads:[~2023-05-04 17:40 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 [this message]
2023-05-04 18:14 ` Katherine Cox-Buday
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='NxF4Z9svIqfZ4ZdSP_LlErXklwpO8siFWZ_aY-KAjK6bfBJ-5xhHJqziFO0pxyQBM4Y79IkCGewvY3Q_2AZETfJ3Rwzrod3OFSwOvm7qov0=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=63267@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@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.