to see if that eliminates the problems. Also I assume Bradley remembered to install the build before running make check. I see lots of libgomp failures I believe those could be due to that. Also, Bradley, did you remember to patch the prune.exp scripts in the testsuite? You will get a huge number of false failures due to linker warnings at -m64 with -g if you don't.
Actually FWIW I agree, the fortran exp (and therefore libgomp) files don't
handle DYLD_LIBRARY_PATH at all, unlike the way that the C and C++ files do. FWIW I'm running the tests right now, and I agree with Jack, other than the failures with isfinite for long double and a couple of other things darwin is remarkably clean in this situation. -eric
