From: Javier Fernandez-Ivern <ivern@acm.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Valdis.Kletnieks@vt.edu, Job 317 <job317@mailvault.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: HELP!! 2.6.x build problem with make xconfig
Date: Sun, 11 Jan 2004 14:12:51 -0800 [thread overview]
Message-ID: <4001CA63.9000300@acm.org> (raw)
In-Reply-To: <m33camdxsq.fsf@defiant.pm.waw.pl>
Krzysztof Halasa wrote:
> Valdis.Kletnieks@vt.edu writes:
>
>
>>>cd /usr/include
>>>rm asm linux scsi
>>>ln -fs /usr/src/linux/include/asm-i386 asm
>>>ln -fs /usr/src/linux/include/linux linux
>>>ln -fs /usr/src/linux/include/scsi scsi
>>
>>Don't do that.
>>
>>Use what's in the glibc-kernheaders RPM for userspace, and let the kernel
>>provide its own headers for its use.
>
>
> GNU libc doesn't have (nor need) its own "kernel" headers and uses the
> kernel ones.
> You may live with "glibc-kernheaders" package only if it matches your
> system. If you're using a different (newer, modified etc) kernel then
> you need the symlinks or a copy (example: new ioctls + programs using
> them).
>
> You may need to recompile the libc as well, if the libc-kernel (binary)
> interface has changed.
Sometimes there's a reason to use the old kernel headers...I still run
several apps that can't grok the 2.6 headers, and will only compile with
2.4 ones (and they work fine). I have a couple of small scripts that
switch the directories around when I need them, for convenience. :)
Of course, the real solution would be to hack them to work with new
headers, but I don't have the time for that at the moment. *Sigh*
--
Javier Fernandez-Ivern
prev parent reply other threads:[~2004-01-11 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 0:00 HELP!! 2.6.x build problem with make xconfig Job 317
2004-01-11 0:19 ` Valdis.Kletnieks
2004-01-11 20:40 ` Krzysztof Halasa
2004-01-11 22:12 ` Javier Fernandez-Ivern [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4001CA63.9000300@acm.org \
--to=ivern@acm.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=job317@mailvault.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox