On Fri, Jul 06, 2018 at 12:30:51PM +0200, Guillermo Rodriguez Garcia wrote: > >> There are no elf files involved. Java > >> applications/libraries can request that a native library is loaded via > >> the System.loadLibrary runtime API. This takes a "generic" (platform > >> independent) library name, which is then "resolved" to a platform > >> specific filename by the JVM. For Windows this is typically "foo" -> > >> "foo.dll", and for Linux it is "foo" -> "libfoo.so". > >> > >> So it seems that removing the .so links breaks all Java applications.. > >> > >> Can this be reconsidered? > > > > No, install_lib is for proper versioned shared libraries. If you need extra > > links, then you can add those with install_link. > > .... however, this is a different case. The problem with Java is not > that the libraries themselves are not properly versioned. The problem > is that due to the way native libraries are loaded in Java, the JVM > must map a "generic" name such as foo to a platform-specific filename, > which for Linux would be "libfoo.so", and then it tries to load that > by filename. This assumes that the .so file is present and links to > the appropriate libfoo.so.X.
And as I said, this is not the intended use-case for install_lib. It makes no sense to install unnecessary links for all libraries just to simplify one obscure corner case. Use install_link to create the necessary symlinks. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected]
