On Fri, Aug 10, 2007 at 02:23:00AM +0200, Julio Meca Hansen wrote:
> Hi,
>
> I would like to ask for creation of the kernel-headers-2.6.22.1 package, as
> it's the current stable kernel version, but the latest
> version that can be found in the ftp is 2.6.21.3, I built my pure64 clfs
> system with the headers in the kernel tarball but I'm not
> sure if I installed them in the correct way, basically I performed the
> following procedure:
>
> install -dv /usr/include
> make mrproper
> make headers_check
> make INSTALL_HDR_PATH=dest headers_install
> cp -av dest/include/{asm-generic,linux,mtd,scsi,sound} /usr/include
> cp -av dest/include/asm-x86_64 /usr/include
>
> system built fine but still... I have some concerns about the procedure being
> 100% safe as I didn't
> copy any header from the asm-i386 subdirectory...
>
My scripts have used the kernel's own headers for some months
without problems on x86* and ppc, but I'm using the old
INSTALL_HDR_PATH=/usr which is known to overwrite userspace headers
on a rebuild. I don't know if the i386 headers are needed or not.
The only problem with doing the simpler cp -av dest/include/*
/usr/include is that it will overwrite the glibc headers (might be
fixed for 2.6.23, or else for 2.6.24, depending on what path the
patch takes to get to linus).
I've heard that other architectures have issues with the kernel's
own headers. Without the hardware, I can't comment. I didn't know
that 2.6.21.3 was in the ftp directory, the book is still at
2.6.20.1. AFAIK I don't have the ability to upload a new headers
tarball, and anyway the kernel's own headers work fine for me -
the one thing you didn't mention is that sysvinit needs a different
patch when used with the kernel's own headers (same patch as in
LFS).
Of course, 2.6.22.2 should be out in the next couple of days
(deadline for comments was 19:00 UTC tonight, if I remember
correctly).
> Also, I have to note at the time of building Mesa, whatever the version it
> is, there's some messages about some
> header files not found, to be exact: stdarg.h, stddef.h, float.h and a quite
> strange behaviour with limits.h
>
> the first 3 files are in the gcc include directory under /usr/lib/<...>, but
> limits.h is actually inside the
> /usr/include hierarchy plus the gcc include file, seems like limit.h recalls
> itself with a macro inside it, is this an error or
> is it fine? seems odd to me...
>
> Julio
Those messages from Mesa are normal. I'm still hoping that by
xorg-7.3 it will use a more normal configure system.
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
