./configure --with-tm fails with PBS 2025.2.1 installed

[dgloe-hpe]

On a SLES 15 SP7 system:

dgloe@cn01:~/prrte-3.0.13> ./configure --with-tm=/opt/pbs
...
--- MCA component ess:tm (m4 configuration macro)
checking for MCA component ess:tm compile mode... static
checking for pbs-config path... /opt/pbs/bin/pbs-config
checking if pbs-config works... no
checking for tm pkg-config name... /opt/pbs/lib/pkgconfig/tm.pc
checking if tm pkg-config module exists... no
checking for tm header at /opt/pbs/include... found
checking for tm library (pbs) in /opt/pbs... found -- lib
checking for tm cppflags... -I/opt/pbs/include
checking for tm ldflags... -L/opt/pbs/lib
checking for tm libs... -lpbs -lcrypto -lz
checking for tm static libs... -lpbs -lcrypto -lz
checking tm.h usability... yes
checking tm.h presence... yes
checking for tm.h... yes
checking for tm_init... no
checking for tm pkg-config name... (cached) /opt/pbs/lib/pkgconfig/tm.pc
checking if tm pkg-config module exists... (cached) no
checking for tm header at /opt/pbs/include... found
checking for tm library (pbs) in /opt/pbs... found -- lib
checking for tm cppflags... -I/opt/pbs/include
checking for tm ldflags... -L/opt/pbs/lib
checking for tm libs... -lpbs -lcrypto -lz
checking for tm static libs... -lpbs -lcrypto -lz
checking for tm.h... (cached) yes
checking for tm_init... (cached) no
checking for tm pkg-config name... (cached) /opt/pbs/lib/pkgconfig/tm.pc
checking if tm pkg-config module exists... (cached) no
checking for tm header at /opt/pbs/include... found
checking for tm library (torque) in /opt/pbs... not found
configure: error: TM support requested but not found.  Aborting
dgloe@cn01:~/prrte-3.0.13> rpm -qa | grep pbs
pbspro-execution-2025.2.1.20250717062818-0.x86_64
pbspro-devel-2025.2.1.20250717062818-0.x86_64

Looking in config.log, the error is:

configure:29102: checking for tm_init
configure:29102: gcc -o conftest -O3 -DNDEBUG  -finline-functions  -I/opt/pbs/include   -L/opt/pbs/lib conftest.c -lm   -lpbs -lcrypto -lz >&5
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libcurl.so.4: undefined reference to `SSL_get0_group_name@OPENSSL_3.2.0'
collect2: error: ld returned 1 exit status

If I build on my own with just -lpbs, everything works, but if I add -lcrypto I get the same failure as in configure.

dgloe@cn01:~/prrte-3.0.13> cat tm.c
#include "tm.h"

int main() {
	tm_init(0, 0);
	return 0;
}
dgloe@cn01:~/prrte-3.0.13> gcc -L/opt/pbs/lib -I/opt/pbs/include -o tm tm.c -lpbs -lcrypto
/usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libcurl.so.4: undefined reference to `SSL_get0_group_name@OPENSSL_3.2.0'
collect2: error: ld returned 1 exit status
dgloe@cn01:~/prrte-3.0.13> gcc -L/opt/pbs/lib -I/opt/pbs/include -o tm tm.c -lpbs
dgloe@cn01:~/prrte-3.0.13>

I think this is because /opt/pbs/lib includes some libraries (like libcrypto, libcurl, libssl) that are also included in /usr/lib.

[rhc54]

Huh - is this something new in how pbs is being deployed? Just wondering why we wouldn't have seen the problem before.

[rhc54]

Also, where did you get PBS 2025.2.1? Trying to figure out if I have a way to reproduce this - I don't have a PBS license, and the latest OpenPBS release is from 2023.

[dgloe-hpe]

You should be able to download PBS Pro RPMs from here (might need to sign up for a free account): https://altairone.com/Marketplace?queryText=PBS&tab=Download&app=PBS+Professional

You won't be able to run any jobs without a license, but you should be able to install the RPMs to reproduce the issue.

[Chrismarsh]

Using the spack stack build of prrte and openmpi, I am building against pbs_version = 2025.2.2.xxxxx without configure problems

[dgloe-hpe]

Looks like the prrte configure fails with PBS 2025.2.1 but works fine with PBS 2025.2.2. Maybe it's a PBS issue that was fixed in 2025.2.2.

[Chrismarsh]

Is the /libs dir in pbs new? I build my full stack using spack so have expectations that the openssl version and libcrypto version are the spack ones. But I am seeing some mixing where libcrypto is from spack but ssl is from pbs. Even if that works for now, it seems like this might become a problem in the future.

[rhc54]

Yes, I believe that is the root cause of the problem. PBS is apparently distributing their own libcrypto, openssl, etc. as part of their package. This causes PRRTE's configure to get into trouble as it sees two copies of those packages in the paths - one from the system, and the other from PBS.

Since PRRTE has a couple of components that need to link against the TM library, that can cause trouble as you wind up with two versions of the system libs in memory - which is why the --with-tm configure check is failing.

[Chrismarsh]

It is probably just luck that the openssl versions match and it "seems to work" in this one specific version. This is obviously going to be crazy brittle.

One option is to ensure everything builds against these "system" curl, ssl, libraries. But that might break other software that requires different versions or options.

[rhc54]

Altair says they are looking into this. Meantime, the simplest solution (if you have ssh access between nodes) is to configure --without-tm so we avoid the multi-library confusion.

[Chrismarsh]

Ok great to hear. I have it working without PBS integration so I hope the lib situation is solved soon