public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Mazur <mmazur@kernel.pl>
To: DervishD <lkml@dervishd.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-libc-headers scsi headers vs libc scsi headers
Date: Thu, 31 Mar 2005 14:26:48 +0200	[thread overview]
Message-ID: <200503311426.48435.mmazur@kernel.pl> (raw)
In-Reply-To: <20050331074526.GA8614@DervishD>

On czwartek 31 marzec 2005 09:45, DervishD wrote:
>     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.

You risk nothing. APIs in linux change incrementally and if kernel hackers do 
want to drop support for an api, they're very vocal about it and it doesn't 
concern stuff that can blow up your computer (see oss vs. alsa).

>     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.

Like I've said, you're unable to break your system this way. And I don't see 
any point in LFS suggesting using raw kernel headers to compile glibc (no you 
*can't* screw up your system by using llh unless I specifically switch ioctls 
so apps remove files instead of opening them; I just can't see any 
possibility to do it by accident).

And I'll add an entry to the llh FAQ to clear this matter up.


-- 
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

  reply	other threads:[~2005-03-31 12:28 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 [this message]
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=200503311426.48435.mmazur@kernel.pl \
    --to=mmazur@kernel.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@dervishd.net \
    /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