RFR: 8352935: Launcher should not add $JDK/../lib to LD_LIBRARY_PATH
Magnus Ihse Bursie
ihse at openjdk.org
Wed Apr 2 15:03:47 UTC 2025
On Tue, 1 Apr 2025 09:13:45 GMT, Joachim Kern <jkern at openjdk.org> wrote:
> In the JDK launcher, there is a codepath which would set/modify the LD_LIBRARY_PATH. This happens unconditionally on AIX and Linux/musl and can also happen on other Linux platforms if an LD_LIBRARY_PATH is pre-set which contains a libjvm.so.
>
> The LD_LIBRARY_PATH is set to $JVMPATH:$JDK/lib:$JDK/../lib. The last part of this, $JDK/../lib, seems to be a remnant of times when there was a jre subfolder in a JDK deployment. So it should likely be removed.
This seems reasonable to me. But there is so much old yucky stuff going on with the JDK bootstrapping issues, that I still get a bit nervous every time someone changes it.
Do you know *why* we do this, i.e. modify LD_LIBRARY_PATH?
-------------
PR Comment: https://git.openjdk.org/jdk/pull/24351#issuecomment-2772870911
More information about the build-dev
mailing list