SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a fresh install of 13.37. I chose defaults for most (maybe all) of the packages, including kernel-headers. I'm trying to build xcpustate but am getting the following error:
In file included from s.c:87:0:
s-linux.c:30:27: fatal error: linux/threads.h: No such file or directory
My glibc version is 2.13 as reported by ldd --version:
ldd (GNU libc) 2.13
The file is at /usr/src/linux-126.96.36.199/include/linux/threads.h
It seems that the files in /usr/include/linux are only a subset of what is in /usr/src/linux/include-188.8.131.52/linux. From what I understand, the files at /usr/include/linux are or should be the ones that libc was built for. I suspect there will be a similar problem with the /usr/include/asm directory.
On my very old linux system (slackware 3... um, yeah, it's been a while...) I recall a similar problem that was solved with some symbolic links but from what I've read that is not the right solution (plus I tried it and it didn't work.)
What's the proper (and hopefully easy) way to resolve this?
It did seem pretty stale. Is there a more modern / maintained tool that provides similar information? I've been out of the Linux scene for a while. There may even be one that came with 13.37 and I just don't know it.