On Solaris, if you set LD_LIBRARY_PATH_64 then that completely overrides any setting of LD_LIBRARY_PATH. If the prevailing environment defines LD_LIBRARY_PATH_64 then the launcher tries to defend itself by prepending its preferred library paths to LD_LIBRARY_PATH, as implemented in the fix for JDK-7029048. That will, however, have no effect -- the launcher should, in this case, prepend its preferred paths to LD_LIBRARY_PATH_64.
- relates to
-
JDK-4810347 jvm STILL exec's itself twice if -d64 or -d32 is used to change data model
-
- Resolved
-
-
JDK-6367077 Purge LD_LIBRARY_PATH usage from the launcher
-
- Closed
-
-
JDK-8216532 tools/launcher/Test7029048.java fails (Solaris)
-
- Resolved
-
-
JDK-7029048 (launcher) fence the launcher against LD_LIBRARY_PATH
-
- Closed
-
-
JDK-8026260 LD_LIBRARY_PATH takes precedence over a runpath (solaris)
-
- Closed
-