From: John Kehayias <john.kehayias@protonmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 63267@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: gcc-toolchain is missing libstdc++.so
Date: Fri, 05 May 2023 20:59:03 +0000 [thread overview]
Message-ID: <87h6sqze9d.fsf@protonmail.com> (raw)
In-Reply-To: <Ep1v1JJOnsfi7wG0QvKyBwOVsowFkmpd4B5orgUDEHZzshS6Xnb_nKaokIlcDbD18XvH4n9DVajid9RPnkd_95UtHfMnYRzR57sj6KadoKw=@protonmail.com>
Hi Kaelyn,
On Thu, May 04, 2023 at 11:45 PM, Kaelyn wrote:
> ------- Original Message -------
> I wasn't sure the best place to share it, so I've attached my "run"
> script for running the binary download of PolyMC in a container. It is
> both a shell script and a guix package manifest, and is the one place
> so far I've worked around the removal of gcc:lib. The main
> program-specific bits are what CMD defaults to and which packages need
> to be included (most of the various shares are to get things like
> hardware 3D, pulseaudio, and dbus working and aren't all always
> needed). It also contains the original manifest commented-out for
> comparison. Hope it can be of help to folks!
>
Thanks, that's a nice little hack! Just something very minor I
noticed, but you don't need to specify glibc directly for the -F (FHS)
option in guix shell, as it will automatically include the (modified)
glibc.
This topic came up again on IRC today and GNUtoo had the correct cli
invocation for getting at gcc:lib. I thought I had tried something
similar but must have missed something, or else didn't notice that
this will only work for guix shell, as guix build doesn't take outputs
in the package list:
--8<---------------cut here---------------start------------->8---
guix shell -e $'(list (@@ (gnu packages gcc) gcc) "lib")'
--8<---------------cut here---------------end--------------->8---
Thanks to both of you I have some options for workarounds currently,
but based on how this topic keeps coming up I still think we should
have a more straightforward option.
John
next prev parent reply other threads:[~2023-05-05 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:50 gcc-toolchain is missing libstdc++.so John Kehayias
2023-05-04 23:45 ` Kaelyn
2023-05-05 20:59 ` John Kehayias [this message]
2023-05-05 23:59 ` Kaelyn
2023-05-08 8:41 ` bug#63267: " Josselin Poiret via Bug reports for GNU Guix
-- strict thread matches above, loose matches on Subject: below --
2023-05-04 14:46 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
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=87h6sqze9d.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=63267@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.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).