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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
