James Snyder

I used to build all the the pre-requisites (at least on OS X) separately with only static libraries which yielded the result you're describing. I see that I'm now sucking...

You could roll back to previous versions that targeted earlier builds. As-is the Makefile doesn't try to interpret anything from the versions to decide what patches to apply, so patches...

They do have quite a few additional options specified. I do periodically look though them when they release new versions, sometimes it's necessary to get them to compile. The path...

On Jan 18, 2012, at 3:27, Liviu [email protected] wrote: > > make it less like generic gcc... > > well, it depends on your objective. I first thought that your...

> in fact my point was exactly opposite, instead of having to deal with aligning the Windows build with the two existing builds (Linux/Mac), I would prefer to use the...

Regarding the first two: Ooops.. I'll fix those as well. Regarding the others, the GCC configuration guide provides some details on that: http://gcc.gnu.org/install/configure.html - --with-sysroot Tells GCC to consider dir...

There's now a branch that uses with-build-time-tools & with-sysroot (with-build-sysroot doesn't really make sense since that's for defining the sysroot for the toolchain being used to build the toolchain.. and...

I presume this is with clang or not otherwise specifying a compiler on a recent version of X-Code on OS X? If I recall this is the main thing that...

I originally had the makefile building those dependencies as well, but switched to homebrew for 2 reasons: 1) mpfr and gmp weren't detecting core i7 machines correctly and were building...

It might also be related to this: https://trac.macports.org/ticket/13499 Here are some similar ones for cross-compiler GCC builds: https://trac.macports.org/ticket/16662 https://trac.macports.org/ticket/16487 Boiling down from these maybe prepending "-L/usr/lib" for the LIBINTL define...