Hi,
Ludovic Courtès writes:
>> Go invokes gcc when compiling with cgo, and cgo (or at least the usage
>> of standard libraries which use cgo) is getting fairly common. If we do
>> not provide a default gcc with Go, a plain "go build" will produce an
>> error if it encounters something which uses
Hi,
Sarah Morgensen skribis:
> Ludovic Courtès writes:
>
>> Hello!
>>
>> It seems that Go unduly retains a reference to GCC:
>>
>> $ guix size go
>> store item total
>> self
>> /gnu/store/g4rrz9rnr8ssbnj3gx3dmsxv4glll8nf-go-1.12.15
Hello,
A quick addendum...
Sarah Morgensen writes:
> This means that even if the user provides a different CC, the
> gcc-7.5.0-lib dir will also be in the runpath. I do not know if, or how
> much, this would conflict with other gcc-lib runpaths.
>
I have just seen the consequences of this: the
Hello all,
(I have CC'd Tobias since we briefly discussed this on #guix recently.)
Ludovic Courtès writes:
> Hello!
>
> It seems that Go unduly retains a reference to GCC:
>
> $ guix size go
> store item totalself
> /gnu/store/g4rrz9rnr8
Hello!
It seems that Go unduly retains a reference to GCC:
--8<---cut here---start->8---
$ guix size go
store item totalself
/gnu/store/g4rrz9rnr8ssbnj3gx3dmsxv4glll8nf-go-1.12.15 646.3
35