CUDA stubs directory must not be added to rpath/runpath

[mboisson]

This is a follow up on easybuilders/easybuild-easyblocks#1464

adding stubs to LIBRARY_PATH is causing us problems, because it ends up in our binaries RUNPATH.

If this happens and you don't use LD_LIBRARY_PATH (because you are using RUNPATH), you will have problems at runtime.

This is probably something you need to check when you are using runpath/rpath with easybuild (for Compute Canada, @bartoldeman had to adjust our linker wrapper to exclude these paths)

A stub object is a shared object, built entirely from mapfiles, that supplies the same linking interface as the real object, while containing no code or data. Stub objects cannot be used at runtime.

[boegel]

@mboisson How are these paths excluded in your linker wrapper exactly? Just based on directory name?

[mboisson]

@bartoldeman would be best to answer that question.

[bartoldeman]

yes, as follows:

        # also exclude stub libraries like for CUDA
        if [ "${1%%/stubs}" != "$1" ]; then
            return 0
        fi

it's not beautiful, but it's unlikely that a directory named "stubs" contains non-stub libraries I would think.

[boegel]

Are there any other cases known besides CUDA? If not, we can consider making the check a bit more strict to also check on CUDA in the path name...

[bartoldeman]

I don't know of any others... in fact if I google /usr/lib64/stubs I only find references to cuda.

[boegel]

How does #2725 look by means of a fix?

[boegel]

fixed via #2725

[bartoldeman]

Note that this issue has resurfaced since easybuilders/easybuild-easyblocks#2373 since the stubs libs are now in $EBROOTCUDA/stubs/lib64.

[boegel]

@bartoldeman So we need to extend the filtering done in #2725 to CUDA/.*/stubs/lib64 or something?

[bartoldeman]

@boegel exactly