glibc and linux-libre-headers

DoneSubmitted by Danny Milosavljevic.
Details
2 participants
  • Danny Milosavljevic
  • Ludovic Courtès
Owner
unassigned
Severity
normal
D
D
Danny Milosavljevic wrote on 8 Aug 2015 01:55
(address . bug-guix@gnu.org)
20150808015559.12b499ac@scratchpost.org
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 ithappen automatically?
With kind regards, Danny
L
L
Ludovic Courtès wrote on 18 Aug 2015 21:23
Re: bug#21216: glibc and linux-libre-headers
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)(address . 21216@debbugs.gnu.org)
87614cieo3.fsf@gnu.org
Danny Milosavljevic <dannym@scratchpost.org> skribis:
Toggle quote (7 lines)> 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 “propagatedinput” of glibc: when glibc is installed in a profile,linux-libre-headers is automatically installed as well. So thereshouldn’t be any problems.
However, instead of installing the ‘glibc’ package, you may want toinstall the ‘gcc-toolchain’ package, which provides all the tools neededto do software development (GCC, libc, Binutils, the ‘ld wrapper’, etc.)
Can you report back?
Thanks,Ludo’.
L
L
Ludovic Courtès wrote on 7 Sep 2015 15:42
control message for bug #21216
(address . control@debbugs.gnu.org)
87h9n6uyzq.fsf@gnu.org
tags 21216 moreinfo
L
L
Ludovic Courtès wrote on 5 Feb 2016 15:08
(address . control@debbugs.gnu.org)
87bn7vi71e.fsf@gnu.org
tags 21216 notabug
L
L
Ludovic Courtès wrote on 5 Feb 2016 15:08
(address . control@debbugs.gnu.org)
87a8nfi713.fsf@gnu.org
close 21216 0.9.1
D
D
Danny Milosavljevic wrote on 16 Feb 2016 19:16
Re: bug#21216: glibc and linux-libre-headers
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 21216@debbugs.gnu.org)
20160216191632.06944fe6@scratchpost.org
Hi,
On Tue, 18 Aug 2015 21:23:40 +0200ludo@gnu.org (Ludovic Courtès) wrote:
Toggle quote (4 lines)> 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
L
L
Ludovic Courtès wrote on 17 Feb 2016 19:15
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)(address . 21216-done@debbugs.gnu.org)
87si0r19v7.fsf@gnu.org
Danny Milosavljevic <dannym@scratchpost.org> skribis:
Toggle quote (11 lines)> On Tue, 18 Aug 2015 21:23:40 +0200> ludo@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 welink.
Toggle quote (2 lines)> Is it documented?
Not yet, but you can help! :-)
Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 21216@debbugs.gnu.org