libstdc++

libstdc++

[Boris A. Dekshteyn]

What package now contains libstdc++? Previously, it was gcc:lib, but now it is
gone.

-- 
WBR, Boris Dekshteyn

Re: libstdc++

[Ludovic Courtès]

Hi,

boris.dekshteyn@gmail.com (Boris A. Dekshteyn) skribis:

> What package now contains libstdc++? Previously, it was gcc:lib, but now it is
> gone.

It’s still there, but the ‘gcc’ package has been “hidden” recently,
meaning that you cannot refer to it by name from the command line.

The reason is that in general you’ll want ‘gcc-toolchain’, not ‘gcc’.
‘gcc-toolchain:lib’ contains libstdc++ and co.

HTH!

Ludo’.

Re: libstdc++

[Boris A. Dekshteyn]

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> It’s still there, but the ‘gcc’ package has been “hidden” recently,
> meaning that you cannot refer to it by name from the command line.

But i can :)
~guix environment --ad-hoc -e '(list (@@ (gnu packages gcc) gcc-9) "lib")'~

> The reason is that in general you’ll want ‘gcc-toolchain’, not ‘gcc’.
> ‘gcc-toolchain:lib’ contains libstdc++ and co.

Why not keep both?

Anyway, ~guix environment --ad-hoc gcc-toolchain:lib~ resulting in these:
--8<---------------cut here---------------start------------->8---
guix environment: error: package `gcc-toolchain@9.1.0' lacks output `lib'
--8<---------------cut here---------------end--------------->8---

in: ~guix environment --ad-hoc gcc-toolchain~
libstdc++, as well some other gcc libs not presented too.

-- 
WBR, Boris Dekshteyn

Re: libstdc++

[Ricardo Wurmus]

Boris A. Dekshteyn <boris.dekshteyn@gmail.com> writes:

>> It’s still there, but the ‘gcc’ package has been “hidden” recently,
>> meaning that you cannot refer to it by name from the command line.
>
> But i can :)
> ~guix environment --ad-hoc -e '(list (@@ (gnu packages gcc) gcc-9) "lib")'~

That’s not the *package* name; this is the *variable* name.

>> The reason is that in general you’ll want ‘gcc-toolchain’, not ‘gcc’.
>> ‘gcc-toolchain:lib’ contains libstdc++ and co.
>
> Why not keep both?

We decided to hide “gcc” because over the past few years people would
often install it when they wanted GCC — a reasonable deduction to make.
But our “gcc” package on its own does not give you a working GCC – the
“gcc-toolchain” package does.  So by hiding the “gcc” package it is much
less likely that someone looking for GCC will end up with a broken package. 

-- 
Ricardo