./configure failed with option '--with-lsf'

[dxyzx0]

Thank you for taking the time to submit an issue!

Background information

What version of Open MPI are you using? (e.g., v3.0.5, v4.0.2, git branch name and hash, etc.)

a992820

Describe how Open MPI was installed (e.g., from a source/distribution tarball, from a git clone, from an operating system distribution package, etc.)

configure from git clone

If you are building/installing from a git clone, please copy-n-paste the output from git submodule status.

9f297ce 3rd-party/openpmix (v1.1.3-3648-g9f297ce)
004d0e8f52bcdafe124eb56f10c2e6c3430cfe7f 3rd-party/prrte (psrvr-v2.0.0rc1-4492-g004d0e8)
+51f3f7de884049c880f45144ae4a63eb6f66f4e4 config/oac (heads/main)

Please describe the system on which you are running

• Operating system/version: Ubuntu 16.04.7 LTS
• Computer hardware: lsf cluster
• Network type: None

---

Details of the problem

I try to configure with '--with-lsf' option but failed in the master branch or 5.0.0rc8 tarball, but succeeded in 4.1.4 tarball.
My command:

shell$ ../configure --with-lsf

The error log in master branch or 5.0.0rc8:

--- MCA component ess:lsf (m4 configuration macro)
checking for MCA component ess:lsf compile mode... static
checking for library containing yp_all... -lnsl
checking for library containing shm_open... -lrt
checking for lsf pkg-config name... /home/abc/opt/lib/lsf/pkgconfig/lsf.pc
checking if lsf pkg-config module exists... no
checking for lsf header at /home/abc/opt/include... found
checking for lsf library (lsf) in /home/abc/opt/lib/lsf... found
checking for lsf cppflags... -I/home/abc/opt/include
checking for lsf ldflags... -L/home/abc/opt/lib/lsf
checking for lsf libs... -llsf -lnsl -lrt
checking for lsf static libs... -llsf -lnsl -lrt
checking lsf/lsf.h usability... yes
checking lsf/lsf.h presence... yes
checking for lsf/lsf.h... yes
checking for ls_info... no
checking for libevent conflict... No conflict found. -levent is not being explicitly used.
configure: WARNING: LSF support requested (via --with-lsf) but not found.
configure: error: Aborting.
configure: ===== done with 3rd-party/prrte configure =====
configure: error: PRRTE configuration failed.  Cannot continue.

But I succeed in 4.1.4.

Upload the config_failed_for_main.log as required in #10943 (comment)
config_failed_for_main.log

I also upload the successful log:
config_4.1.4.log

[rhc54]

@jjhursey @awlauria Your area - any thoughts?

[jsquyres]

@dxyzx0 Is the cited git hash at or near the HEAD of the main branch?

EDIT: Oops, I see your reference to "main" later in the text. Can you attach the config.log file from the failed run?

[jjhursey]

From the output posted it looks like the library found didn't have the symbol needed. The check for ls_info is here.

The config.log should show the error message and compile string that it tried.

If you know where the LSF libraries are located you can try specifying the exact path to --with-lsf and maybe also --with-lsf-libdir (the lib dir is not always at the same level as the other LSF binaries in bin depending on the installation).

[awlauria]

Did the lsf configure logic change between v4.1 and v5.0? Perhaps there is a typo in the main/v5.0 branches.

[awlauria]

Well, checking prte, the main and v3 logic hasn't changed in 7 months:
https://github.com/openpmix/prrte/blob/master/config/prte_check_lsf.m4

[dxyzx0]

@dxyzx0 Is the cited git hash at or near the HEAD of the main branch?

EDIT: Oops, I see your reference to "main" later in the text. Can you attach the config.log file from the failed run?

@jsquyres I upload the config_failed_for_main.log in the post.

From the output posted it looks like the library found didn't have the symbol needed. The check for ls_info is here.

The config.log should show the error message and compile string that it tried.

If you know where the LSF libraries are located you can try specifying the exact path to --with-lsf and maybe also --with-lsf-libdir (the lib dir is not always at the same level as the other LSF binaries in bin depending on the installation).

@jjhursey I have tried to set the --with-lsf=path_to_include and --with-lsf-libdir=path_to_lib in the main branch. In 4.1.4, I can pass the check just with --with-lsf.
I think the problem maybe lies in this line

checking for lsf pkg-config name... /home/abc/opt/lib/lsf/pkgconfig/lsf.pc
checking if lsf pkg-config module exists... no

Since, I compare the log with the succeeded one in 4.1.4, which doesn't have this check. And I can't find this lsf.pc file in my lsf installation folder.
I also upload the succeeded config_4.1.4.log in the post.

[rhc54]

Well, checking pate, the main and v3 logic hasn't changed in 7 months

Quite true (assuming you meant "v5" instead of "v3")- but I believe it has changed significantly from your v4 series.

Since, I compare the log with the succeeded one in 4.1.4, which doesn't have this check. And I can't find this lsf.pc file in my lsf installation folder.

It didn't find the package config file, but the configure logic did go ahead using your provided settings. It found the required header files, but failed to find the expected function symbol in the library. I think that is the heart of the problem, but I leave it to the IBM folks to resolve.

[awlauria]

Well, checking pate, the main and v3 logic hasn't changed in 7 months

Quite true (assuming you meant "v5" instead of "v3")- but I believe it has changed significantly from your v4 series.

Well I meant prrte v3.0, which would be ompi v5 yes.

[awlauria]

Removed the blocker label since there is a documented work-around:

@dxyzx0 Is the cited git hash at or near the HEAD of the main branch?
EDIT: Oops, I see your reference to "main" later in the text. Can you attach the config.log file from the failed run?

@jsquyres I upload the config_failed_for_main.log in the post.

From the output posted it looks like the library found didn't have the symbol needed. The check for ls_info is here.
The config.log should show the error message and compile string that it tried.
If you know where the LSF libraries are located you can try specifying the exact path to --with-lsf and maybe also --with-lsf-libdir (the lib dir is not always at the same level as the other LSF binaries in bin depending on the installation).

@jjhursey I have tried to set the --with-lsf=path_to_include and --with-lsf-libdir=path_to_lib in the main branch. In 4.1.4, I can pass the check just with --with-lsf. I think the problem maybe lies in this line

checking for lsf pkg-config name... /home/abc/opt/lib/lsf/pkgconfig/lsf.pc
checking if lsf pkg-config module exists... no

Since, I compare the log with the succeeded one in 4.1.4, which doesn't have this check. And I can't find this lsf.pc file in my lsf installation folder. I also upload the succeeded config_4.1.4.log in the post.

@dxyzx0 just to confirm, did using --with-lsf=path_to_include and --with-lsf-libdir=path_to_lib work-around your issue with main?

[dxyzx0]

@awlauria No. Still not work. In config_failed_for_main.log, you can check I set these two parameters but still not work.

[awlauria]

Thanks - adding the blocker label back.