LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-16-2006, 12:56 PM   #1
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,453

Rep: Reputation: Disabled
kernel headers and glibc


Seeking enlightenment...

In the KernelHeaders.WARNING file it says:

Quote:
As a general rule, installing kernel headers
that are newer than the kernel glibc was compiled with *may* cause problems,
so unless you need these for a particular reason it's best to stick with the
2.4.x kernel-headers package for now.
...and so I've never installed the kernel headers for the 2.6.x kernels. In the current/Changelog it says:

Quote:
glibc-2.3.6-i486-6.tgz: Recompiled against 2.4.33.3 and 2.6.17.13 headers
So does that mean I can/should install the 2.6.17 kernel headers?

Thanks in advance,

Brian
 
Old 09-16-2006, 01:21 PM   #2
nykey
Member
 
Registered: Nov 2003
Location: Tg-Jiu, Romania
Distribution: OpenSUSE 11.1 / echo "Windows XP" > Trash
Posts: 360

Rep: Reputation: 30
That means you CAN install the 2.6.x kernel-headers but you SHOULD stick with the 2.4.x for now, unless you need them for something which explicitly requires the 2.6.x kernel-headers.
 
Old 09-16-2006, 01:35 PM   #3
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,453

Original Poster
Rep: Reputation: Disabled
So what does he mean when he says that glibc was compiled against 2.6.17 headers? I'm just trying to get my mind around this.

Thanks,
Brian
 
Old 09-16-2006, 01:36 PM   #4
zetabill
Member
 
Registered: Oct 2005
Location: Rhode Island, USA
Distribution: Slackware, Xubuntu
Posts: 348

Rep: Reputation: 30
I was under the impression that it was an 'or' situation rather than an 'and' situation. As I understand it, you could have either the 2.4 headers or the 2.6 headers that Pat compiled. I, for one, was looking forward to having a 2.4-free system and compiling glibc against both headers was the solution for that.

Everything I find on this subject is the same song I've heard but I haven't found anything that makes much sense to me as far as not being able to compile against both headers. Really... my question is whether or not it is possible to compile against both sets of headers and still get the same glibc package. Logic says it's not possible, I know... but Pat's changelog leads me to believe otherwise.

So basically... despite the changelog saying that glibc is compatible to both... 2.4 headers for glibc and 2.6 headers for kernel-du-jour as usual? I'm very confused.
 
Old 09-16-2006, 01:59 PM   #5
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,123

Rep: Reputation: 151Reputation: 151
I don't know how (or if) you can compile against 2 versions - but here's what running /lib/libc-2.3.6.so on my Slackware -current system outputs:
Code:
/lib/libc-2.3.6.so
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.4.6.
Compiled on a Linux 2.4.33.3 system on 2006-09-14.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        linuxthreads-0.10 by Xavier Leroy
        BIND-8.2.3-T5B
        libthread_db work sponsored by Alpha Processor Inc
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
 
Old 09-16-2006, 03:29 PM   #6
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Here's how you get it:
Code:
mingdao@test:~$ /lib/libc-2.3.6.so
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.4.6.
Compiled on a Linux 2.4.33.3 system on 2006-09-14.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        linuxthreads-0.10 by Xavier Leroy
        BIND-8.2.3-T5B
        libthread_db work sponsored by Alpha Processor Inc
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
Code:
mingdao@test:~$ /lib/tls/libc-2.3.6.so
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.4.6.
Compiled on a Linux 2.6.17.13 system on 2006-09-14.
Available extensions:
        GNU libio by Per Bothner
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
        NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.
I must admit to more ignorance than understanding here. But someone
such as Alien Bob will come along and add clarity -- bank on it.

I wanted an entire Slackware-11.0 RC4 2.6.17.13 system. This one was
installed with huge26.s, than afterwards these were added:
Code:
mingdao@test:~$ ls -l /var/log/packages/kernel-*2.6.17.13*
-rw-r--r-- 1 root root     963 2006-09-16 08:02 /var/log/packages/kernel-generic-2.6.17.13-i486-1
-rw-r--r-- 1 root root   43671 2006-09-17 03:51 /var/log/packages/kernel-headers-2.6.17.13-i386-1
-rw-r--r-- 1 root root  103482 2006-09-16 08:00 /var/log/packages/kernel-modules-2.6.17.13-i486-1
-rw-r--r-- 1 root root 1328332 2006-09-16 08:01 /var/log/packages/kernel-source-2.6.17.13-noarch-1
When you install with huge26.s, the first boot says the kernel is
2.6.17.13. But the only thing in the system relating to 2.6.17.13
at that point is /boot/vmlinuz, which is NOT a symlink. It is only
the kernel image from ../slackware-current/kernels/huge26.s/bzImage.

You must reboot and install everything else or you still have ONLY
the 2.4.33.3 modules, headers, source, and config file.
 
Old 09-17-2006, 01:02 AM   #7
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 124Reputation: 124
Originally posted by BCarey
Quote:
So what does he mean when he says that glibc was compiled against 2.6.17 headers?
Read Pat's comments in these files, as well as the -current ChangeLog:
Code:
./slackware-current/README.NPTL
./slackware-current/RELEASE_NOTES
If you'll notice from my post above, glibc is installed in two separate
$PATHs. One uses the 2.4.33.3 headers; the other uses 2.6.17.13 headers.

Maybe you don't need the 2.6 headers as nykey stated; but if you do,
they are available.

I ran rt2500.SlackBuild and built okay.
 
Old 09-17-2006, 09:37 PM   #8
zetabill
Member
 
Registered: Oct 2005
Location: Rhode Island, USA
Distribution: Slackware, Xubuntu
Posts: 348

Rep: Reputation: 30
At the risk of sounding thick-headed:

Reading those files tells me that, at the very least, the 2.4 headers should be installed and the 2.6 headers are a good idea if using any sort of 2.6 kernel.

Am I remotely close?
 
Old 09-17-2006, 09:42 PM   #9
win32sux
Guru
 
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870

Rep: Reputation: 371Reputation: 371Reputation: 371Reputation: 371
basically, you wanna stick with the 2.4 headers (even if you're running kernel 2.6) unless you have some specific need for the 2.6 ones... and if you use the 2.6 ones, make sure you use the version glibc was compiled with, not a newer kernel-of-the-day version...

Last edited by win32sux; 09-17-2006 at 09:45 PM.
 
Old 09-17-2006, 09:56 PM   #10
zetabill
Member
 
Registered: Oct 2005
Location: Rhode Island, USA
Distribution: Slackware, Xubuntu
Posts: 348

Rep: Reputation: 30
Got it... that's what I figured.

What I was trying to ask in my last post was 2.4 headers are a given and 2.6 headers were an option when using a 2.6 kernel. My question has been answered, though.

Thanks.
 
  


Reply

Tags
kernel headers, slackware11


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Glibc Unable to Find Kernel Headers Kenji Miyamoto Linux From Scratch 6 12-30-2008 04:03 PM
the first gcc in CLFS1 do not need the Glibc headers of target? augustus Linux From Scratch 2 09-16-2006 08:36 AM
FC5 glibc-headers snt Fedora 4 03-26-2006 02:37 PM
Glibc w/ 2.6 headers chbin Slackware 4 04-15-2005 08:06 AM
send packets with kernel routing and without kernel messing with headers bassdemon Programming 5 02-08-2005 06:29 PM


All times are GMT -5. The time now is 05:31 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration