You're basically telling your build system to use a C++ compiler as the linker when creating libtorque. This probably does more-or-less what I suggested: rpath'ing in whatever dependencies you need such that when we link against libtorque, all of the (C++) dependencies that you need are automatically pulled along.
Glad it got resolved!
On Jan 28, 2013, at 4:55 PM, David Beer <dbeer_at_[hidden]>
> On Mon, Jan 28, 2013 at 12:14 PM, Barrett, Brian W <bwbarre_at_[hidden]> wrote:
> On 1/28/13 11:54 AM, "David Beer" <dbeer_at_[hidden]> 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.
> Thanks for your help. I found a way to resolve this by changing OpenMPI's configure script, but then someone who knows a bit more about these things showed me that we can solve this by defining some more things on our end, namely adding:
> to our configure.ac and
> +LIBTOOL_DEPS = @LIBTOOL_DEPS@
> +libtool: $(LIBTOOL_DEPS)
> + $(SHELL) ./config.status --recheck
> to our Makefile.am. I'm going to try to look some things up and see why this makes a difference, but I'm guessing that we previously had an incomplete definition that confused OpenMPI's configure script. Thanks for all of your help and I'm glad we could resolve this by fixing TORQUE.
> David Beer | Senior Software Engineer
> Adaptive Computing
> devel mailing list
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/