SEO

Hi,

I just wanted to check stg in the kernel config options, so as usual,
in /usr/src/linux I've typed:
make menuconfig

the output was:
-------------------------
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:201: error: `PATH_MAX' undeclared (first use in this
function)
scripts/basic/fixdep.c:201: error: (Each undeclared identifier is reported
only once
scripts/basic/fixdep.c:201: error: for each function it appears in.)
scripts/basic/fixdep.c:201: warning: unused variable `s'
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:297: error: `PATH_MAX' undeclared (first use in this
function)
scripts/basic/fixdep.c:297: warning: unused variable `s'
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2
-------------------------


I thought I have mixed up stg in the source, so I have deleted the whole,
and unpacked again from the original linux-2.6.13.4.tar.gz .
The result is the same.
What went wrong? Any idea?

Thanks,
Dudee

> I thought I have mixed up stg in the source, so I have deleted the whole,
> and unpacked again from the original linux-2.6.13.4.tar.gz .
> The result is the same.
> What went wrong? Any idea?
>
> Thanks,
> Dudee

Hmm..I think I have found the problem, but I am not very familiar with this
stuff, so maybe some of you could help me
So, I have found out that I have removed the package - that came with 10.2 -
kernel-headers-2.4.31.
Can this cause the problem that I have described before?
If yes, what to do? These headers are in the source, so simply copy them
to /usr/include ?


Thanks,
Dudee

Dudee Bastardo wrote:


>
> Hmm..I think I have found the problem, but I am not very familiar with
> this stuff, so maybe some of you could help me
> So, I have found out that I have removed the package - that came with 10.2
> - kernel-headers-2.4.31.
> Can this cause the problem that I have described before?
> If yes, what to do? These headers are in the source, so simply copy them
> to /usr/include ?

It's me again!
I have just read the "kernel-headers" thread, and found that I sohuld stick
with the 2.4 headers, thus put back the original package.
Am I right?

Dudee

On Mon, 13 Feb 2006 00:58:13 +0100, Dudee Bastardo wrote:

> Dudee Bastardo wrote:
>
>
>>
>> Hmm..I think I have found the problem, but I am not very familiar with
>> this stuff, so maybe some of you could help me
>> So, I have found out that I have removed the package - that came with 10.2
>> - kernel-headers-2.4.31.
>> Can this cause the problem that I have described before?
>> If yes, what to do? These headers are in the source, so simply copy them
>> to /usr/include ?
>
> It's me again!
> I have just read the "kernel-headers" thread, and found that I sohuld stick
> with the 2.4 headers, thus put back the original package.
> Am I right?
>
> Dudee

You need the kernel headers to compile source code. Don't confuse kernel
headers with linux kernel source.

Dudee Bastardo wrote:
> Dudee Bastardo wrote:
>
>
>
>>Hmm..I think I have found the problem, but I am not very familiar with
>>this stuff, so maybe some of you could help me
>>So, I have found out that I have removed the package - that came with 10.2
>>- kernel-headers-2.4.31.
>>Can this cause the problem that I have described before?
>>If yes, what to do? These headers are in the source, so simply copy them
>>to /usr/include ?
>
>
> It's me again!
> I have just read the "kernel-headers" thread, and found that I sohuld stick
> with the 2.4 headers, thus put back the original package.
> Am I right?
>
> Dudee

Yes, you should reinstall the kernel header package. It installs
into /usr/include, and everything except the kernel source
will compile using the headers there.

The kernel source headers should be in /usr/src/linux/include.
You can run any kernel you like, but the system kernel headers
should be the ones that the system's C library was compiled with.