[gentoo-user] Re: Vmware modules doesn't build for gentoo-2.6.9-gentoo-r3 kernel

[Georgi Georgiev]

On Tue, 07 Dec 2004 00:02:49 +0100, Bastian Balthazar Bux wrote:

> Martin Larsson wrote:
>
>>On Tue, 9 Nov 2004 11:58:14 -0600, Chris Cox <onebeer32@×××××××.com>
>>wrote:
>>
>>
>>>What is the location of the directory of C header files that match your
>>>running
>>>kernel? [/lib/modules/2.6.9-gentoo-r3/build/include]
>>>
>>>
>>>
>>Maybe your header files are in /usr/src/linux/include ?

Or maybe you're using KERNEL_OUTPUT? In that case vmware modules
compilation fails badly before it has started. You can get my patched
ebuilds from my personal portage overlay at
rsync://rsync.gg3.net/gentoo-portage-chutz/app-emulation/vmware-workstation/.
These cut out large portions of vmware-config.pl that do nothing but ask
silly questions (like "where are your headers", since it is gentoo policy
that /usr/src/linux should point to your current kernel) and also patch
the appropriate makefiles.

> the ones installed by sys-kernel/linux26-headers are in
> /usr/include/linux. BTW can someone explain me why this package exist?
> It's not enaugh the linux ones, the only answer I can give myself is not
> to be constricted to recompile a bunch of programs every time u change
> kernel. It's the right answer ?

glibc compiles against the headers in /usr/include/linux.
Programs that link against glibc (read: all programs) need to include the
headers that glibc was built against in order to link properly. These
headers need to always correspond to the version that glibc was compiled
against. Hence the warnings that the linux-headers ebuild spits out at
installation, reminding you to recompile glibc next.

-- 
 )   Georgi Georgiev    ) Anyone who has had a bull by the tail         )
(     chutz@×××.net    (  knows five or six more things than someone   (
 )  [phone]    ) who hasn't. -- Mark Twain                     )



--
gentoo-user@g.o mailing list