cross-compilation documentation

[Jan-Benedict Glaw]

On Sun, 2003-06-22 13:19:50 -0400, Andrew Pinski <pinskia@physics.uc.edu>
wrote in message <BB15CB3A-A4D5-11D7-AD8C-000393A6D2F2@physics.uc.edu>:
> It is documented, just not fully:
> 
> "that each --with option has a corresponding --without option"
> 
> --with-headers
> --with-headers=dir
> Deprecated in favor of --with-sysroot.  Specifies that target headers 
> are available when building a cross compiler.  The dir argument 
> specifies a directory which has the target include files.  These 
> include files will be copied into the gcc install directory.  This 
> option with the dir argument is required when building a cross 
> compiler, if prefix/target/sys-include doesn't pre-exist.  If 
> prefix/target/sys-include does pre-exist, the dir argument may be 
> omitted.  fixincludes will be run on these files to make them 
> compatible with GCC.

<USER type="newbie">
	Say I want to give --with-headers, what exactly should I place
	there, in which structure? Let's start with some example
	combination: Linux as the OS and arm as it's platform. I do have
	nothing but kernel and glibc sources.

	How (and which) glibc headers shall I fetch? Taken those which
	would appear in /usr/include/ at a target system, should I place
	these into the directory I specify at --with-headers? ...or do I
	have to place them into <--with-headers-DIR>/usr/include/ ?
	
	How do I have to treat Linux headers? All headers? Only the
	./include/linux/ part? The ./include/linux/asm part? (How shall
	I do this for ARM where, in 2.5.x, we have subarch support?)
	What's about the asm-generic part? Where to place those?
</USER>

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20030622/a71f3cf1/attachment.sig>