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 automat
On Mon, Jan 28, 2013 at 12:14 PM, Barrett, Brian W wrote:
> On 1/28/13 11:54 AM, "David Beer" 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
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'
On 1/28/13 11:54 AM, "David Beer" 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
I don't see anything in the config script that checks for gcc - you might take
a look at it to check. It's in config/orte_check_tm.m4 on our developer's trunk
On Jan 28, 2013, at 10:54 AM, David Beer wrote:
>
> On Mon, Jan 28, 2013 at 10:54 AM, Barrett, Brian W wrote:
>
> We assume that we c
On Mon, Jan 28, 2013 at 10:54 AM, Barrett, Brian W wrote:
>
>
> We assume that we can link lib torque into a C application (if this is a
> problem for you, it's a huge deal breaker for us, since OMPI is a C
> library). What does config.log say when checking for tm_init?
>
> Brian
>
>
Brian,
libto
On 1/28/13 10:50 AM, "David Beer" wrote:
> By way of introduction, I'm a TORQUE developer and I probably should've joined
> this list - even if only to keep myself informed - years ago.
>
> At any rate, we're in the process of changing TORQUE so that it compiles using
> g++ instead of gcc. We're