Thank you for all this information. Your diagnosis is totally right. I actually sent e-mail yesterday but apparently it never got through :<
It IS the MPI application that is failing to link, not OpenMPI itself; my e-mail was not well written; sorry Brice. The situation is this: I am trying to compile using an OpenMPI 1.5.4 that was built to be rooted in /release, but it is not placed there yet (testing); it is currently under /builds/release. I have set OPAL_PREFIX in the environment, with the intention of helping the compiler wrappers work right. Under /release, I currently have OpenMPI 1.4.3, whereas the OpenMPI under /builds/release is 1.5.4. What I am getting is this: The mpif90 wrapper (under /builds/release/openmpi/bin) puts -I/release instead of -I/builds/release. But it includes -L/builds/release. So I'm getting headers from 1.4.3 when compiling, but the libmpi from 1.5.4 when linking. I did a quick "move 1.4.3 out of the way and put 1.5.4 over to /release where it belongs" test, and my application did link without errors, so I think that confirms the nature of the problem. Is it a bug that mpif90 didn't pay attention to OPAL_PREFIX in the -I but did use it in the -L ? -----Original Message----- From: users-boun...@open-mpi.org [mailto:users-boun...@open-mpi.org] On Behalf Of Jeff Squyres Sent: Friday, September 30, 2011 7:04 AM To: Open MPI Users Subject: Re: [OMPI users] EXTERNAL: Re: Unresolved reference 'mbind' and 'get_mempolicy' I think the issue here is that it's linking the *MPI application* that is causing the problem. Is that right? If so, can you send your exact application compile line, and the the output of that compile line with "--showme" at the end? On Sep 29, 2011, at 4:24 PM, Brice Goglin wrote: > Le 28/09/2011 23:02, Blosch, Edwin L a écrit : >> Jeff, >> >> I've tried it now adding --without-libnuma. Actually that did NOT fix the problem, so I can send you the full output from configure if you want, to understand why this "hwloc" function is trying to use a function which appears to be unavailable. > > This function is likely available... in the dynamic version of libnuma > (that's why configure is happy), but make is probably trying to link > with the static version which isn't available on your machine. That's my > guess, at least. > >> I don't understand about make V=1. What tree? Somewhere in the OpenMPI build, or in the application compilation itself? Is "V=1" something in the OpenMPI makefile structure? > > Instead of doing > ./configure ... > make > do > ./configure <same options> > make V=1 > > It will make the output more verbose. Once you get the failure, please > send the last 15 lines or so. We will look at these verbose lines to > understand how things are being compiled (which linker flags, which > libraries, ...) > > Brice > > _______________________________________________ > 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
