From: NightStrike <nig...@gm...> - 2010-04-21 19:30:29
|
On Wed, Apr 21, 2010 at 11:41 AM, Doug Semler <dou...@gm...> wrote: > Well, it looks like the compiler may be being built with host != > target... In other words it wasn't bootstrapped and has been > configured as a cross compiler... > > LIBRARY_PATH is ignored in cross compilers. That's because it is a cross compiler > The buildbot that builds this should probably override the > configuration guess, by both passing the --host=x86_64-w64-mingw32 on > the configure line, and also by passing --enable-bootstrap if it's > being built on a 64 windows machine. I don't know how well this would > work, but it could be tried.... > > If host != target, CROSS_DIRECTORY_STRUCTURE is defined, which then > turns off several environment variables (that wouldn't be suitable for > a cross compiler)... The toolchain in question is host=win32 target=win64. So it is meant to cross compile from a 32-bit windows generating binaries for a 64-bit windows. It just so happens that you can run this on win64, since win64 can run win32 programs. But that doesn't mean that we should treat it like it's not a cross compiler. |