I don't claim to understand the inner workings of gcc, particularly on the mac but I ran into the exact same issue you're having a week or so back. As William pointed out the issue is with the -g flag being passed which for some unknown reason seems to result in the test programs compiling as OSX applications, hence that directory organization you were seeing, and then failng to run as the configure script cannot locate the executable. If you just run the configure script with out any CFLAGS you should be able to get things at least compiling, 'env CFLAGS="" ./configure' is what worked for me. -- View this message in context: http://www.nabble.com/build-problems-on-Mac-OS-X-10.5.2.-tp17140529p17143187.html Sent from the Grass - Dev mailing list archive at Nabble.com.
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
