From: DervishD <lkml@dervishd.net>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Mariusz Mazur <mmazur@kernel.pl>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-libc-headers scsi headers vs libc scsi headers
Date: Thu, 31 Mar 2005 17:40:39 +0200 [thread overview]
Message-ID: <20050331154039.GB6468@DervishD> (raw)
In-Reply-To: <Pine.LNX.4.62.0503311659040.7825@jjulnx.backbone.dif.dk>
Hi Jesper :)
* Jesper Juhl <juhl-lkml@dif.dk> dixit:
> > > And I don't see any point in LFS suggesting using raw kernel
> > > headers to compile glibc
> > I don't know their reasons because I haven't read any rationale
> > (if any exists at all). Anyway, I've used LLH (including the scsi
> http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html seems to have a
> bearing on what you are discussing - just FYI.
Not exactly. My doubt is not about whether use symlinks to linux
and asm in the linux kernel or not, is about using what glibc people
prefer or seem to prefer (raw kernel headers) or using llh. I know
that I don't have to use the current kernel headers in /usr/include,
but the ones used when compiling my libc or (better) llh.
Thanks anyway :)
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...
prev parent reply other threads:[~2005-03-31 15:40 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
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 [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=20050331154039.GB6468@DervishD \
--to=lkml@dervishd.net \
--cc=juhl-lkml@dif.dk \
--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