This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> 1. Get a life, install Linux... ;) I would do SW dev there but.. you know. > 2. Build a Linux-to-mingw32 (or Linux-to-cygwin-b20) cross-toolset. > > 3. Build a Linux-to-h8300 cross-toolset (needed to build h8300-libs) > > 4. Build a mingw32-to-h8300 cross-toolset using the 2. and 3. toolsets. > (This is called the 'Canadian cross' -- Please see the Cross-GCC FAQ) Actually I managed to do this OK. But when I tested the mingw32-h8300 cross toolset, h8300-hms-gcc test.c somehow managed to call i386-as claiming 'c:\tmp\tjaetj.s this is not a legal i386 instruction'. Compiling with h8300-hms-gcc -S test.c and h8300-hms-as test.s worked ok though. Does somebody have an idea about this: building binutils-2.9.1 (the newest?) to --target=h8300-hms is OK when --host=i586-linux but when i586-cygwin32/mingw32 is involved (ie. compiling mingw/cygwin cross h8300-hms in linux or compiling target=h8300-hms in cygwin fails at srconv.c)? In Linux I can build binutils-2.9.1 without problems at all. _______________________________________________ New CrossGCC FAQ: http://www.objsw.com/CrossGCC _______________________________________________ To remove yourself from the crossgcc list, send mail to crossgcc-request@cygnus.com with the text 'unsubscribe' (without the quotes) in the body of the message.