Can't compile libnfnetlink and libnetfilter_conntrack
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
No problems on a clean slack-12 with kernel 2.6.21.5,
identical compilers, same compiler setup.
With your kernel 2.6.23.9 the included linux/headers could be different.
(See "programs.c" #include linux/.....h)
It compiles fine on Slackware 12.0 with a custom 2.6.24.4 kernel (gcc 4.1.2 -- default Slack 12). When you compiled your kernel, did you install the kernel headers as well? (That would be a bad thing -- you should never upgrade the kernel headers. gcc, glibc and other stuff was built against the 2.6.21.5 kernel headers included in Slackware, and therefore you could get compile errors if you upgrade the kernel headers).
What do you mean with 'did I installed the kernel headers'? It is custom compiled kernel and sources are still in the same directory - /home/ivanatora/Archives/linux-2.6.23.9/
I have /usr/src/linux/ symlinked to that directory.
ivanatora, you don't need the symlink from /usr/src/linux to your kernel source directory -- it'll pick it up just fine (though you can always keep the symlink if you want, since in Slackware, at least, it doesn't break anything). When you compiled your kernel, how did you install it? There's a command like `make install_headers` that some poorly written kernel compilation guides will tell you to use, which is totally wrong. gcc, glibc, etc. were built against the 2.6.21.5 kernel headers, and therefore the kernel headers should never be upgraded. The best (or one of the best) guide(s) to follow is Alien Bob's kernel compilation guide, here: http://alien.slackbook.org/dokuwiki/...kernelbuilding
`ls /var/log/packages/kernel-headers-2.6.21.5*` should return something. If it doesn't, you removed (or didn't install...?) the kernel-headers package. Download it from your favourite Slackware mirror and install it (using `installpkg packagename.tgz`). If you DID install the kernel headers when you compiled your kernel, but the kernel-headers package is still installed, you could try `upgradepkg --reinstall packagename.tgz` to attempt to reinstall the headers (it's possible that some /usr/include/* files were overwritten by your kernel headers, if you did install them).
Other than that I can't help you (I don't have any other guesses as to why it would/wouldn't work, unless you didn't do a full install and you're missing a dependency somewhere).
You probably need to et rid of the symlink from /usr/src/linux to your non-standard kernel sources. Many programs expect the included headers to be the same in /usr/include/linux and /usr/src/linux/include. the link /usr/src/linux should point to the original version of the sources which are distributed with Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.