Ludovic Courtès wrote:
> I tried hard to avoid
> having a wrapper at all but came to the conclusion that this was the
> best we could do
Can something be done to avoid that installing the packages 'glibc' and
'binutils' shadows this wrapper?
Maybe moving the wrapper to a different package than
Hi Danny,
Danny Milosavljevic skribis:
> I remember being tripped up by this when I started using Guix. It is
> annoying.
>
> I wonder if it's possible to instruct gcc (or ld, I guess) to automatically
> add rpath to where it found the respective library. That's really what we
> expect to
Hello,
zimoun skribis:
> Compiling Fortran leads to the same issue, if I understand correctly.
> Is it not the reason of the addition of 'gfortran-toolchain'?
> And I guess it should be the same issue for the other front-ends that
> GCC supports (Ada, etc.), isn't it?
>
> Well, is it not GCC
Hi Ludo,
On Mon, 4 May 2020 at 11:32, Ludovic Courtès wrote:
> > Packages needed for C development
> > =
> >
> > For C development, you will typically need the packages
> > make gcc-toolchain gdb
> >
> > Do NOT install glibc and binutils explicitly,
Hi,
Bruno Haible skribis:
> The question "What packages do I need to do normal C development?" should
> really be documented.
>
> How about a doc section - at the beginning of the chapter
> https://guix.gnu.org/manual/en/html_node/Development.html - that says:
>
> Packages needed for C
Dear Bruno,
Thank you for your feedback.
On Mon, 4 May 2020 at 01:10, Bruno Haible wrote:
> > Another way to do software development is with ‘guix environment’:
> >
> > https://guix.gnu.org/manual/en/html_node/Development.html
> >
> > For example, if you want to hack on Gettext, run:
> >
>
Hi Ludo,
> > $ guix install make gcc-toolchain binutils glibc gdb gettext m4 autoconf
> > automake
>
> It’s a mistake to explicitly binutils and glibc: they are provided by
> ‘gcc-toolchain’ along with an ‘ld’ wrapper that takes care of adding
> entries to the RUNPATH of binaries:
>
>
>
Hi,
Bruno Haible skribis:
> $ guix install make gcc-toolchain binutils glibc gdb gettext m4 autoconf
> automake
It’s a mistake to explicitly binutils and glibc: they are provided by
‘gcc-toolchain’ along with an ‘ld’ wrapper that takes care of adding
entries to the RUNPATH of binaries:
Hi,
I'm using the recent guix-system-vm-image-1.1.0.x86_64-linux.
After installing a couple of package for development
$ guix install make gcc-toolchain binutils glibc gdb gettext m4 autoconf
automake
I expected to be able to build GNU bison 3.5.91 from source. But I hit a build
failure, due to
