From: Kaelyn <kaelyn.alexi@protonmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: 63267@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: gcc-toolchain is missing libstdc++.so
Date: Fri, 05 May 2023 23:59:19 +0000 [thread overview]
Message-ID: <1pOI6MV7sx3-zolxwH99rQ93RMcbp677fn9twoyv4ZhNBhicZgnNC4bI_u0-aJCfLOjBDb_q8wmu_JihwNW7ECzh-RUmTn3c4jwfd2BCz-4=@protonmail.com> (raw)
In-Reply-To: <87h6sqze9d.fsf@protonmail.com>
------- Original Message -------
On Friday, May 5th, 2023 at 8:59 PM, John Kehayias <john.kehayias@protonmail.com> wrote:
>
>
> 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.
Thanks! A small side note: I have glibc in there mainly so ldd is available for debugging problems or getting new binaries working (I think the comment with it is a remnant of an older version of the manifest from before "-F" was added to "guix shell").
Cheers,
Kaelyn
next prev parent reply other threads:[~2023-05-06 0:00 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
2023-05-05 23:59 ` Kaelyn [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='1pOI6MV7sx3-zolxwH99rQ93RMcbp677fn9twoyv4ZhNBhicZgnNC4bI_u0-aJCfLOjBDb_q8wmu_JihwNW7ECzh-RUmTn3c4jwfd2BCz-4=@protonmail.com' \
--to=kaelyn.alexi@protonmail.com \
--cc=63267@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@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 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.