Prev: Logitech usb camera.
Next: no sound on my hp dv7 notebook using alsa
From: .Martin. on 1 Nov 2009 04:44
Hi all,

I upgraded my Slackware 13 to Slackware-current. Additionally, I
compiled a new kernel (31.5). Everything works fine, apart from one
thing: I can't compile new programs. When I ./configure or use sbopkg I
get the following errors:

> /usr/include/bits/local_lim.h:39:26: error: linux/limits.h: No such file or directory

or somethimes:

> configure: error: C preprocessor "/lib/cpp" fails sanity check

I can guess why I get such errors. I probably don't heave kernel-headers
for the new kernel. I removed the packages related to the stock-29.x kernel.
When I check the slackware website, even the testing packages contain
30.5 kernel. What am I supposed to do?
My /usr/src/ looks like that:
> drwxr-xr-x 2 root root 4096 2009-10-05 21:23 ati
> lrwxrwxrwx 1 root root 14 2009-11-01 02:34 linux -> linux-2.6.31.5
> drwxrwxr-x 24 root root 4096 2009-11-01 02:34 linux-2.6.31.5
> lrwxrwxrwx 1 root root 27 2009-10-28 19:26 vboxdrv-3.0.8 -> /opt/VirtualBox/src/vboxdrv
> lrwxrwxrwx 1 root root 30 2009-10-28 19:26 vboxnetadp-3.0.8 -> /opt/VirtualBox/src/vboxnetadp
> lrwxrwxrwx 1 root root 30 2009-10-28 19:26 vboxnetflt-3.0.8 -> /opt/VirtualBox/src/vboxnetflt


Thank you

Regards
Martin

From: Henrik Carlqvist on 1 Nov 2009 06:55
".Martin." <xtd8865(a)gmail.com> wrote:
> I compiled a new kernel (31.5). Everything works fine, apart from one
> thing: I can't compile new programs. When I ./configure or use sbopkg I
> get the following errors:
>
>> /usr/include/bits/local_lim.h:39:26: error: linux/limits.h: No such
>> file or directory

> I can guess why I get such errors. I probably don't heave kernel-headers
> for the new kernel.

You are not supposed to have kernel headers for your new kernel. When
compiling programs you are supposed to have the same kernel headers which
was used to compile your installed glibc.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: .Martin. on 1 Nov 2009 07:45
Henrik Carlqvist wrote:
> ".Martin." <xtd8865(a)gmail.com> wrote:
>> I compiled a new kernel (31.5). Everything works fine, apart from one
>> thing: I can't compile new programs. When I ./configure or use sbopkg I
>> get the following errors:
>>
>>> /usr/include/bits/local_lim.h:39:26: error: linux/limits.h: No such
>>> file or directory
>
>> I can guess why I get such errors. I probably don't heave kernel-headers
>> for the new kernel.
>
> You are not supposed to have kernel headers for your new kernel. When
> compiling programs you are supposed to have the same kernel headers which
> was used to compile your installed glibc.
>
> regards Henrik

Thanks for your reply. Does that mean that I'm supposed to install the
kernel-headers for the stock slackware kernel (29.x)?

regards
Martin
From: goarilla on 1 Nov 2009 09:37
On Sun, 01 Nov 2009 12:45:29 +0000, .Martin. wrote:

> Henrik Carlqvist wrote:
>> ".Martin." <xtd8865(a)gmail.com> wrote:
>>> I compiled a new kernel (31.5). Everything works fine, apart from one
>>> thing: I can't compile new programs. When I ./configure or use sbopkg
>>> I get the following errors:
>>>
>>>> /usr/include/bits/local_lim.h:39:26: error: linux/limits.h: No such
>>>> file or directory
>>
>>> I can guess why I get such errors. I probably don't heave
>>> kernel-headers for the new kernel.
>>
>> You are not supposed to have kernel headers for your new kernel. When
>> compiling programs you are supposed to have the same kernel headers
>> which was used to compile your installed glibc.
>>
>> regards Henrik
>
> Thanks for your reply. Does that mean that I'm supposed to install the
> kernel-headers for the stock slackware kernel (29.x)?
>
> regards
> Martin

maybe you can fix it differently
it seems /usr/include/linux/limits.h doesn't exist

it ought to be the same file as /usr/src/linux/include/linux/limits.h
so maybe you could copy /usr/src/linux/include/linux to /usr/include/

because i don't think the kernel headers from 29.x vs 31.5
differ that much (someone mentioned 30.x and onwards are the same)

i don't know if it's the right way to do tho
iirc most distro's seem to symlink /usr/src/linux/include/linux to /usr/
include/linux. while in slackware the kernel headers are seperate files
from /usr/src/linux

eg the same files reside 2 times in the filesystem instead of only once
yes i checked it with hashes eg /usr/include/linux/ and /usr/src/linux/
include/linux containt he exact same files (except one is missing
compile.h) while beeing seeded by 2 seperate packages eg: kernel-source
and kernel-headers.
From: Henrik Carlqvist on 1 Nov 2009 11:47
".Martin." <xtd8865(a)gmail.com> wrote:
> Henrik Carlqvist wrote:
>> you are supposed to have the same kernel headers which
>> was used to compile your installed glibc.

> Does that mean that I'm supposed to install the
> kernel-headers for the stock slackware kernel (29.x)?

Yes, reinstalling the kernel-headers package will give you the right .h
files which match your installed glibc.

There is one possible case when headers matching the used kernel is needed
and that is when compiling kernel modules. However, mostly you will only
compile normal programs and then these headers are the ones that you want.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

 |  Next  |  Last
Pages: 1 2 3
Prev: Logitech usb camera.
Next: no sound on my hp dv7 notebook using alsa