delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/12/13/19:01:37

From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: cross compiled linux kernel under cygwin NT
13 Dec 1998 19:01:37 -0800 :
Message-ID: <199812132001.OAA11533.cygnus.gnu-win32@modi.xraylith.wisc.edu>
References: <3671D695 DOT 1E4E AT ou DOT edu>
To: "Hugh.M.Bright-1" <Hugh DOT M DOT Bright-1 AT ou DOT edu>
Cc: gnu-win32 AT cygnus DOT com

"Hugh.M.Bright-1" <Hugh DOT M DOT Bright-1 AT ou DOT edu> writes:
> today i cross compiled a linux kernel (2.1.105) for 
> intel x86 using cygwin b20.1 as host and a gcc-2.8.1 configged as a
> cross compiler to i486-pc-linux-gnu. the linux kernel booted from a
> floppy. i didnt get a chance to test it. 
> 
> anyways
> it took only alot of twiddling, nothing major.
> im no expert on this stuff.

There is really nothing magical about cross-builds, provided the build
process itself does not need to run the target binaries for configuration
etc. The twiddling is needed since nobody has yet fixed the configuration
and building process with x-compilation in mind.

I'm assuming you know the caveats of building Linux kernels using 
gcc-2.8.x or egcs-1.x (search the linux kernel lists for description 
of the problem -- mostly invalid asms used in the linux kernel which 
worked with gcc 2.7.2, but not any more). Detailed description is well
beyond the scope of this forum.

I don't know if 2.1.x has all the fixes necessary. 2.0.x certainly does
not. Building these kernels with egcs is asking for trouble.

Regards,
Mumit

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019