--- Original Message ---
On Friday, May 5th, 2023 at 8:59 PM, John Kehayias
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 runni
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 th
--- Original Message ---
On Thursday, May 4th, 2023 at 9:50 PM, John Kehayias
wrote:
> > 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
Hi all,
> 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
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 t
Hi again,
On Thu, May 04, 2023 at 11:19 AM, John Kehayias wrote:
> 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++.
Hi,
--- Original Message ---
On Thursday, May 4th, 2023 at 3:26 PM, John Kehayias
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.
> >
>
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 writes:
>
>>
>> Hello All,
>>
>> I noticed today that libstdc++.so.1 (and some others), which u
Sorry for the spam; Resending this without the bugs address, but with
the issue's address.
Christopher Rodriguez writes:
> [[PGP Signed Part:Undecided]]
>
> 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 o
