From: DervishD <lkml@dervishd.net>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-libc-headers scsi headers vs libc scsi headers
Date: Thu, 31 Mar 2005 09:45:26 +0200 [thread overview]
Message-ID: <20050331074526.GA8614@DervishD> (raw)
In-Reply-To: <200503302240.08200.mmazur@kernel.pl>
Hi Mariusz :)
* Mariusz Mazur <mmazur@kernel.pl> dixit:
> On ?roda 30 marzec 2005 20:10, DervishD wrote:
> > Yes, I know, this is in the llh FAQ, but the answer starts with
> > 'Not too sure on this one', that's the reason I'm asking here...
> Use whatever works. And ignore anybody telling you, that your system will blow
> up if you use the wrong headers to compile something.
The fact is that, in the past, I've used kernel headers older
than my running kernel for building glibc and my system worked
seamlessly (although I don't use bleeding edge features, you know),
but I don't want to take risks.
I don't know which set of headers will work, and in fact I don't
know if I must follow 'Linux From Scratch' advice and use raw kernel
headers for building glibc and LLH headers for any other thing. I
think I probably will use the LLH headers (including scsi) for
everything since glibc passes the 'make check' doing that... If I
screw my system badly, I have lotsa backups at hand.
Thanks for your advice :)
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736
http://www.dervishd.net & http://www.pleyades.net/
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-03-31 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 16:21 linux-libc-headers scsi headers vs libc scsi headers DervishD
2005-03-30 18:10 ` DervishD
2005-03-30 20:40 ` Mariusz Mazur
2005-03-31 7:45 ` DervishD [this message]
2005-03-31 12:26 ` Mariusz Mazur
2005-03-31 14:17 ` DervishD
2005-03-31 15:00 ` Jesper Juhl
2005-03-31 15:40 ` DervishD
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=20050331074526.GA8614@DervishD \
--to=lkml@dervishd.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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