Re: Linus's include file strategy redux

[Joe deBlaquiere <jadb@redhat.com>]

My solution to this has always been to make a cross compiler environment 
(even if it is the same processor family). Thusly i386-linux-gcc knows 
that the target system's include files are in:

/usr/local/<project>-tools/i386-linux/include (/linux, /asm)

The other advantage to this is that I can switch my host environment 
(within reason - compatible host glibcs, ok) and not have to change the 
target compiler.

Werner Almesberger wrote:

> ferret@phonewave.net wrote:
> 
>> Just out of curiosity, what would happen with redirection if your source
>> tree for 'the currently running kernel' version happens to be configured
>> for a different 'the currently running kernel', perhaps a machine of a
>> foreign arch that you are cross-compiling for?
> 
> 
> Two choices:
>  1) try to find an alternative. If there's none, fail.
>  2) make the corresponding asm or asm/arch branch available (non-trivial
>     and maybe not desirable)
> 
> 
>> I do this: I use ONE machine to compile kernels for five: four i386 and
>> one SUN4C. My other machines don't even HAVE /usr/src/linux, so where does
>> this redirection leave them?
> 
> 
> Depends on your distribution: if it doesn't install any kernel-specific
> headers, you wouldn't be able to compile programs requiring anything
> beyond what it provided by your libc. Otherwise, there could be a
> default location (such as /usr/src/linux is a default location now).
> 
> The main advantage of a script would be that one could easily compile
> for multiple kernels, e.g. with
> 
> export TARGET_KERNEL=2.0.4
> make
> 
> Even if your system is running 2.4.13-test1.
> 
> The architecture could be obtained from the tree or the tree could be
> picked based on the architecture. This is a policy decision that could
> be hidden in the script.
> 
> - Werner


-- 
Joe deBlaquiere
Red Hat, Inc.
307 Wynn Drive
Huntsville AL, 35805
voice : (256)-704-9200
fax   : (256)-837-3839

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/