Subj : Re: How to overcome compilation errors?
To   : comp.os.linux
From : nobody
Date : Thu Aug 26 2004 10:54 pm

Occam <occam@internode.razoron.net> spewed this unto the Network: 
> On Mon, 23 Aug 2004 19:10:43 -0700, Durk van Veen <nospamplz@example.com> wrote:
> 
>>Occam wrote:
>>
>>> I am running Skackware 10 with kernel 2.6.7, and have compiled several
>>> programs that are not included in Slack 10 - no problems.
>>
>>In general the kernel headers that you are compiling against should match
>>the kernel version used to compile your version of glibc, not necessarily
>>the version that you boot up with. If you replaced the kernel headers when
>>you installed your most recent kernel, this may account for some weird
>>behavior.

> Thanks,
> I checked and found that the 'original' 2.4.26 stuff is overwritten with 2.6.7
> data - but only in /usr/src/linux-2.4.26.  Normally my /usr/src/linux is a
> symlink to the current kernel, and this is the case now too; only the target
> directory has a misleading name.  This is the first time, however, that I do not
> have all kernel sources saved.
> 
> The stuff in /usr/include/asm and /usr/include/linux are still the files from
> 2.4.26 (according to dates).  Question: Am I compiling against these headers, or
> the 'originals' in /usr/src/linux/... ? 

You are compiling against the old headers in /usr/include/linux. If
you're gonna keep the kernel source lying around, one thing you could do
is make /usr/include/linux a symlink to /usr/src/linux/include/linux, and
/usr/include/asm a symlink to /usr/src/linux/include/linux.

.