GNU bug report logs - #21216
glibc and linux-libre-headers

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21216 in the body.
You can then email your comments to 21216 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: bug-guix <at> gnu.org
Subject: Re: glibc and linux-libre-headers
Date: Sat, 8 Aug 2015 01:55:59 +0200

Hello,

I installed GuixSD recently and ran into the same problem as there:

https://lists.gnu.org/archive/html/bug-guix/2013-02/msg00032.html

Installing linux-libre-headers manually did help, but shouldn't it
happen automatically?

With kind regards,
   Danny

Message #8 received at 21216 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 21216 <at> debbugs.gnu.org
Subject: Re: bug#21216: glibc and linux-libre-headers
Date: Tue, 18 Aug 2015 21:23:40 +0200

Danny Milosavljevic <dannym <at> scratchpost.org> skribis:

> I installed GuixSD recently and ran into the same problem as there:
>
> https://lists.gnu.org/archive/html/bug-guix/2013-02/msg00032.html
>
> Installing linux-libre-headers manually did help, but shouldn't it
> happen automatically?

Nowadays, unlike in Feb. 2013, linux-libre-headers is a “propagated
input” of glibc: when glibc is installed in a profile,
linux-libre-headers is automatically installed as well.  So there
shouldn’t be any problems.

However, instead of installing the ‘glibc’ package, you may want to
install the ‘gcc-toolchain’ package, which provides all the tools needed
to do software development (GCC, libc, Binutils, the ‘ld wrapper’, etc.)

Can you report back?

Thanks,
Ludo’.

Message #17 received at 21216 <at> debbugs.gnu.org (full text, mbox):

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 21216 <at> debbugs.gnu.org
Subject: Re: bug#21216: glibc and linux-libre-headers
Date: Tue, 16 Feb 2016 19:16:32 +0100

Hi,

On Tue, 18 Aug 2015 21:23:40 +0200
ludo <at> gnu.org (Ludovic Courtès) wrote:

> However, instead of installing the ‘glibc’ package, you may want to
> install the ‘gcc-toolchain’ package, which provides all the tools needed
> to do software development (GCC, libc, Binutils, the ‘ld wrapper’, etc.)

I tried that now - that works fine. 

Why can I install glibc (when it doesn't work anyway)? What's the difference?
Is it documented?

Thanks.

Regards,
   Danny

Message #20 received at 21216-done <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym <at> scratchpost.org>
Cc: 21216-done <at> debbugs.gnu.org
Subject: Re: bug#21216: glibc and linux-libre-headers
Date: Wed, 17 Feb 2016 19:15:40 +0100

Danny Milosavljevic <dannym <at> scratchpost.org> skribis:

> On Tue, 18 Aug 2015 21:23:40 +0200
> ludo <at> gnu.org (Ludovic Courtès) wrote:
>
>> However, instead of installing the ‘glibc’ package, you may want to
>> install the ‘gcc-toolchain’ package, which provides all the tools needed
>> to do software development (GCC, libc, Binutils, the ‘ld wrapper’, etc.)
>
> I tried that now - that works fine. 
>
> Why can I install glibc (when it doesn't work anyway)? What's the difference?

The most important difference is the linker wrapper (“ld-wrapper”),
which makes sure -Wl,-rpath is passed for each library against which we
link.

> Is it documented?

Not yet, but you can help!  :-)

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.