JDK-6367072 : Hotspot should not depend on LD_LIBRARY_PATH
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.3.1,5.0,6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic,linux,solaris_8
  • CPU: generic,sparc
  • Submitted: 2005-12-23
  • Updated: 2017-09-14
  • Resolved: 2009-12-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6367077 - Purge LD_LIBRARY_PATH usage from the launcher
Description
Remove dependency on LD_LIBRARY_PATH for Linux as runpath information is in the shared libraries now and this can be used like it's done for Solaris. This is a dependency for a launcher improvement to eliminate it's setup of LD_LIBRARY_PATH. See the notes in 4777947 for history and additional details.
Comments
EVALUATION This issue is fixed via 6367077, closing this as a duplicate.
01-12-2009
EVALUATION The getenv(3C) was eliminated in the VM for 6312057 on Solaris to set the java.library.path property, this was done by using dlinfo(3C), however on linux there is no visible support for dlinfo. There are references on the web that it has been introduced since taroon/severn/rawhide release, still no man page for this, however a nm on ld.so does yield a dlinfo function. This can be implemented only when the minimum Java supported config for Linux supports the dlinfo(3C) function, unless we take back door approaches to query the dynamic linker(ld.so) for LD_LIBRARY_PATH, which is a very risky alternative.
04-05-2006