This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Fwd: GCC 3.1 linux-to-mingw32 near success but still some questions remain ;-)


On Sunday 14 July 2002 21:08, you wrote:
> ----------  Forwarded Message  ----------
> Subject: GCC 3.1 linux-to-mingw32 near success but still some questions
> remain ;-)
> Date: Sun, 14 Jul 2002 21:02:22 +0200
> From: Pieter Thysebaert <pieter.thysebaert@intec.rug.ac.be>
> To: crossgcc@sourceware.cygnus.com
>
>
> Hello,
>
> First of all, congrats to myself for being able to at least compile
>  <subject>.
>

Ok, I've solved most problems myself:

1) Only untarring the headers and mingw runtime in prefix/target is necessary 
(not in prefix)

2) configure enabled long-long IO support....but strtoull and strtoll are 
nowhere on my system, so re-doing the last step with --disable-long-long 
worked fine!
    Why is this not detected during the configure pass?

3) Why did I have to patch the ld/pe-dll.c file?

4) Using my fresh mingw32 cross compiler and binutils, I wanted to build 
native mingw32 binutils and gcc.

However,

mkdir build-native-binutils
cd build-native-binutils
../binutils.../configure --prefix=/temp/native-tools --host=i686-pc-mingw32 
--target=i686-pc-mingw32 --build=i686-pc-linux-gnu
make

Ends with an error because of conflicting type definitions in 
libiberty/strerror.c and the mingw32 stdlib.h for "str_errorlist"

Any thoughts on that one?

Pieter



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]