From: Pieter T. <pie...@in...> - 2003-09-15 07:28:07
|
On Sunday 14 September 2003 11:36, Tom wrote: > Dear Pieter, > > Thanks very much for your reply. I understand a little better now that I > can't expect gcc to work "out of the box":) I tried 3.3.1 and a 3.4 CVS > snapshot on msys and 3.4 on linux, they failed with a parse error in a file > I can't remember the name of. I also yesterday tried a 3.4 snapshot on > cygwin which failed because it couldn't find a file. When you say that > cross compiling works in 3.4 CVS do you mean the mingw cvs or the main gcc > cvs? I am only interested in building 3.4 because I want to try out the PCH > support, but for now I will use the mingw 3.3.1 candidate I built on msys > to compile my software. I mean the main gcc CVS. I tried it last week or so with w32api 2.3 and the then-latest mingw runtime. Is is the minimal cross-compiler build that fails? I configured that with ../gcc/configure --host=i686-pc-cygwin --target=i686-pc-mingw32 --build=i686-pc-cygwin --disable-threads --enable-languages=c --prefix=/usr/local/cross-tools Don't forget that you should now build w32api and then mingw runtime, and install them (i.e. configure with "--prefix=") in /usr/local/cross-tools/i686-pc-mingw32 (note the "target"-subdir below the gcc install dir) For the full cross-compiler I changed that to ".... --enable-threads --enable-languages=c,c++,java --enable-libgcj ..." This worked for me, although I have not tested precompiled headers. Pieter |