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 directory Homebrew uses, which were being called instead of the correct Homebrewed 64 bit libraries. Best, Raiden On Mon, Dec 2, 2013 at 4:02 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>wrote: > 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 which may be faulty, or may accidentally be referring to > the libraries of the other (therefore resulting in Badness). > > > > On Dec 2, 2013, at 3:52 PM, Raiden Hasegawa <raiden.haseg...@gmail.com> > wrote: > > > Yes, what I meant is that when running: > > > > /usr/local/bin/gfortran -o conftest conftest.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) < > jsquy...@cisco.com> wrote: > > On Dec 2, 2013, at 3:00 PM, Raiden Hasegawa <raiden.haseg...@gmail.com> > 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: checking if Fortran compiler works > > configure:29635: /usr/local/bin/gfortran -o conftest conftest.f >&5 > > Undefined symbols for architecture x86_64: > > "__gfortran_set_options", referenced from: > > _main in cccSAmNO.o > > ld: symbol(s) not found for architecture x86_64 > > collect2: error: ld returned 1 exit status > > configure:29635: $? = 1 > > configure: program exited with status 1 > > configure: failed program was: > > | program main > > | > > | end > > configure:29651: result: no > > configure:29665: error: Could not run a simple Fortran program. > Aborting. > > ----- > > > > Did you typo and mean that the compiler does work when outside of > configure, and fails when it is inside 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? > > > > Do you have DYLD_LIBRARY_PATH set? > > > > -- > > Jeff Squyres > > jsquy...@cisco.com > > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
