On Tue, Sep 21, 2010 at 4:35 AM, Ruben Van Boxem <[email protected]> wrote: > 2010/9/20 Ruben Van Boxem <[email protected]> >> >> Here's my configure line: >> >>> /home/Ruben/mingw64/src/gmp/configure --host=i686-w64-mingw32 >>> --build=i686-w64-mingw32 CFLAGS="-mtune=core2 -fomit-frame-pointer >>> -momit-leaf-frame-pointer" --prefix=/home/Ruben/mingw64/build32/gcc-libs >>> --disable-static --enable-shared --enable-cxx > > > Strange but true: the problem lies in the first bit of the above configure > line: the absolute path... It seems that caused configure to get confused, > not find some gmp conftest headers, and make very wrong assumptions about my > build environment. I removed all absolute paths from my build script, just > to be sure nothing else has problems with this. 32-bit build is coming up :)
Yes, this is due to some custom GMP m4 macros that fail miserably when using absolute paths. We recently pulled all of that out of the buildbot scripts and the makebuildroot files. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
