romio314: do not link with cudart

[minrk]

identical to #9144 for libcuda, applied to libcudart as well

This commit forces ROMIO to not detect cudart at configure time by using setting the hidden/undocumented ac_cv_lib_cudart_cudaStreamSynchronize=no variable before invoking ROMIO's configure.

Refs:

• romio314: do not link with CUDA #9144 introduced the same patch for detection of libcuda using ac_cv_lib_cuda_cuMemGetAddressRange=no
• cuda: libmpi.so.0 links libcuda.so which causes link issues when cuda is not installed #8884 describing libcuda issue (same issue happens with libcudart)
• fix and test for improper cuda linkage conda-forge/openmpi-feedstock#186 shows building openmpi with --with-io-romio-flags=ac_cv_lib_cudart_cudaStreamSynchronize=no fixes the cudart link, suggesting this patch will work

Signed-off-by: Min RK [email protected]

[github-actions]

Hello! The Git Commit Checker CI bot found a few problems with this PR:

da50c9d: romio314: do not link with cudart

• check_signed_off: does not contain a valid Signed-off-by line

Please fix these problems and, if necessary, force-push new commits back up to the PR branch. Thanks!

[minrk]

I'm not sure how syncing with upstream works, but fwiw current MPL (since mpich 4.0, I think) uses a newer PAC_CHECK_HEADER_LIB_OPTIONAL, which looks like it would allow --with-cuda=no to stop looking for and linking libcuda and libcudart instead of setting these ac_cv_ variables.

[ggouaillardet]

FWIW #12640 is a romio updrade (from MPICH 4.2.1). It is still a draft because I had no time to test it.
I think the job is done though.