Thanks Jeff,
It turns out this was an issue with Homebrew (package manager for mac) and
not related to open-mpi...
If any Homebrew users have this issue in the future when installing
open-mpi here's what happened: there were some non-Homebrewed 32-bit
gfortran libraries floating around in the lib
I did notice that you have an oddity:
- I see /usr/local/opt/gfortran/bin in your PATH (line 41 in config.log)
- I see that configure is invoking /usr/local/bin/gfortran (line 7630 and
elsewhere in config.log)
That implies that you have 2 different gfortrans installed on your machine, one
of wh
Yes, what I meant is that when running:
/usr/local/bin/gfortran -o conftestconftest.f
outside of configure it does work.
I don't think I have DYLD_LIBRARY_PATH set, but I will check when I get
back to my home computer.
On Mon, Dec 2, 2013 at 3:47 PM, Jeff Squyres (jsquyres)
wrote:
> On De
On Dec 2, 2013, at 3:00 PM, Raiden Hasegawa wrote:
> Thanks, Jeff. The compiler does in fact work when running the troublesome
> line in ./configure.
Errr... I'm not sure how to parse that. The config.log you cited shows that
the compiler does *not* work in configure:
-
configure:29606:
Thanks, Jeff. The compiler does in fact work when running the troublesome
line in ./configure. I haven't set either FC, FCFLAGS nor do I have
LD_LIBRARY_PATH set in my .bashrc. Do you have any thoughts on what
environmental variable may trip this up?
Raiden
On Mon, Dec 2, 2013 at 11:23 AM, Jef
It looks like your Fortran compiler installation is borked. Have you tested
with the same test program that configure used?
program main
end
Put that in a simple "conftest.f" file, and try the same invocation line that
configure used:
/usr/local/bin/gfortran -o conftest
Hi All, new to the list here. I'm running into an error while trying to
configure:
shell$ ./configure --prefix=/usr/local/Cellar/open-mpi/1.7.3
--disable-silent-rules --enable-ipv6
Here is a blurb from the config.log (which I have attached as well):
configure:29606: checking if Fortran compiler
