Greetings, all.

I recently installed Slackware 10.2 on my laptop. I got the source for kernel 2.6.16.5 and compiled, compilation works. After rebooting, I realize I got a few things wrong and need to re-compile. When I go to /usr/src/linux and type my normal 'make menuconfig', I get:

HOSTCC scripts/basic/fixdep
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:144,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.6/include/limits.h:122,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.6/include/syslimits.h:7,
from /usr/lib/gcc-lib/i486-slackware-linux/3.3.6/include/limits.h:11,
from scripts/basic/fixdep.c:113:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
In file included from /usr/include/sys/socket.h:35,
from /usr/include/netinet/in.h:24,
from /usr/include/arpa/inet.h:23,
from scripts/basic/fixdep.c:115:
/usr/include/bits/socket.h:304:24: asm/socket.h: No such file or directory
scripts/basic/fixdep.c: In function `use_config':
scripts/basic/fixdep.c:214: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:214: error: (Each undeclared identifier is reported only once
scripts/basic/fixdep.c:214: error: for each function it appears in.)
scripts/basic/fixdep.c:214: warning: unused variable `s'
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:310: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:310: warning: unused variable `s'
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2

and that's it.
I've seen posts elsewhere suggesting a (re)installation of libc6-dev; I can find no corresponding slackware package for this library. I've reinstalled cxxlib:
cxxlibs-6.0.3-i486-1 [inst=yes]: cxxlibs (C++ shared library compatibility package)
which I believe contains libc6, but no change.

Any ideas?

cheers,
~ben

Try reinstalling glibc:
http://slackware.it/en/pb/package.ph...c-2.3.6-i486-2

Thanks for the quick response, mdarby.
OK, reinstalled glibc (upgraded, actually; my version was 2.3.5), still the same problem -- exactly the same output.
Anything else?

cheers,
~ben

I believe you hadn't uninstalled kernel headers after successful kernel compilation, because socket.h is form kernel headers package.

Well actually, I _did_ uninstall the kernel headers.

Specifically, I removed the package kernel-headers-2.4.31-i386-1.tgz, which is necessary for compilation... there's not a kernel-headers-2.6.xx yet (maybe in Slack 11?), AFAIK, so you have to keep this package around. I had known this at some time in the past, but forgot. I will not forget again

Thanks for the help!

cheers,
~ben

Sorry, I realize I was unclear. Reinstalling the package kernel-headers-2.4.31-i386-1.tgz fixed the problem.

~ben

My previous post was retorical question and not some kind of unquestionable statement. Sorry for confusing.

That's scary because that should NOT have fixed your problem.

You installed kernel headers from a 2.4 kernel yet you're building a 2.6 kernel? Doesn't sound right to me. Well, maybe it does. It sounds like there are links to the 2.4 kernel sources in your /usr/include directory. This practice is one that can lead to problems, other than what you've encountered.

According to the glibc maintainers, copies of the kernel headers should be placed in /usr/include (copies of the asm and linux directories from the kernel source) and not links.

Personally, I use sym links since I'm lazy BUT I have links to the kernel source for the kernel I'm actually running.

So, can you post the output from:

$ ls -ld /usr/include/asm
$ ls -ld /usr/include/linux

Thanks!

Peace...

Because he has installed kernel-headers package, real kernel headers reside in /usr/include (not their symlinks).

That's cool but my concern is he has kernel headers for a 2.4 kernel installed in /usr/include and not 2.6 headers.

Peace...

That's fine. As I understand it, headers in /usr/src/linux should be those against which glibc was compiled. This has nothing to do with the currently running kernel. See lkml post and other related info here, here, and here. I'm not sure it's been completely resolved even now.

Look here: http://www.slackware.at/data/slackwa...eaders.WARNING