On Sun, Feb 02, 2003 at 12:21:22AM -0000, Elfyn McBratney wrote:
>Sorry, could not be arsed to reformat this... :-)
>
>Im pretty sure, it makes sense to me and kinda confirmed in the mknetrel
>script, that Chris (cgf) uses cross gcc, binutils and maybe more that are
>targetted for i{3,4,5,6?}86-pc-cygwin... So you'd need to compile at very
>least a cross-compiler for cygwin.
Yes, I use a linux x cygwin gcc+binutils for all of my cygwin work. That's
sort of stock in trade for my division of Red Hat (the division formerly
known as Cygnus).
I use the "uberbaum" repository to check out everything in one tree:
cvs -d :pserver:[EMAIL PROTECTED]:/cvs/uberbaum login
cvs -d :pserver:[EMAIL PROTECTED]:/cvs/uberbaum co .
This is the configure line I used to build everything:
/path/to/source/configure --target=i686-pc-cygwin --build=i686-pc-linux \
--host=i686-pc-linux --prefix=/somewhere --disable-nls \
--enable-languages=c++ --enable-sjlj-exceptions
And then use:
make all install
To install it.
This creates i686-pc-cygwin-gcc, i686-pc-cygwin-ld, i686-pc-cygwin-as, etc.
that are used to build cygwin.
There is a mailing list for discussing cross gcc:
[EMAIL PROTECTED]
Before someone asks, I built the cross compiler myself, I'm not willing
to make it available for general distribution, and I'm not willing to
act as a mentor to other enterprising souls who want to do the same
thing. There are surely web sites out there which deal with this issue.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
