Skip to content

Conversation

@ocaisa
Copy link
Member

@ocaisa ocaisa commented May 7, 2025

It's come up in EESSI that setting this can be useful when using the GCC compiler directly, see https://www.eessi.io/docs/using_eessi/building_on_eessi/#manually-building-software-on-top-of-eessi-without-easybuild

Basically with this change, instead of having to do

export LD_RUN_PATH=$LIBRARY_PATH:$EBROOTGCCCORE/lib64

to get a working executable, you would just need

export LD_RUN_PATH=$LIBRARY_PATH

which requires less explaining.

@ocaisa
Copy link
Member Author

ocaisa commented May 7, 2025

This is not a correct fix and has actually been already addressed in #3584 (see https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/g/gcc.py#L206-L212)

@ocaisa ocaisa closed this May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant