I'll +1 what Brian said: we *really* don't want to have to link Open MPI with a C++ compiler.
Can't you rpath in whatever support libraries you need (e.g., the g++ libraries with the cxx_personality symbol), such that when we -ltorque, it just pulls in whatever other dependencies it needs? (I'm assuming that you're extern "C"'ing all the tm_*() function calls so that they can be called from C code, not C++ code) On Jan 28, 2013, at 2:14 PM, "Barrett, Brian W" <bwba...@sandia.gov> wrote: > On 1/28/13 11:54 AM, "David Beer" <db...@adaptivecomputing.com> wrote: > >> checking for tm_init in -ltorque... no >> configure: error: TM support requested but not found. Aborting >> >> Oddly enough, if you have already configured with an older version of >> TORQUE, you can build open-mpi with TORQUE 4.2 installed, so it can find the >> function definitions when compiling, its just for some reason it doesn't >> find them in the configure script. This is why I think that something in the >> configure script is assuming that libtorque was compiled with gcc. > > Right, the configure output to stdout/stderr isn't very useful in diagnosing > why a test failed. The config.log file generated by configure will have much > more information. > > Brian > > -- > Brian W. Barrett > Scalable System Software Group > Sandia National Laboratories > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
