glibc and linux-libre-headers

  • Done
  • quality assurance status badge
Details
2 participants
  • Danny Milosavljevic
  • Ludovic Courtès
Owner
unassigned
Submitted by
Danny Milosavljevic
Severity
normal

Debbugs page

Ludovic Courtès wrote 10 years ago
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 “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’.
Ludovic Courtès wrote 10 years ago
control message for bug #21216
(address . control@debbugs.gnu.org)
87h9n6uyzq.fsf@gnu.org
tags 21216 moreinfo
Ludovic Courtès wrote 9 years ago
(address . control@debbugs.gnu.org)
87bn7vi71e.fsf@gnu.org
tags 21216 notabug
Ludovic Courtès wrote 9 years ago
(address . control@debbugs.gnu.org)
87a8nfi713.fsf@gnu.org
close 21216 0.9.1
Danny Milosavljevic wrote 9 years ago
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 +0200
ludo@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
Ludovic Courtès wrote 9 years ago
(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 we
link.

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 an email to 21216@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 21216
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help