[jdk17] RFR: 8269668: [aarch64] java.library.path not including /usr/lib64

[Severin Gehwolf]

On Fri, 2 Jul 2021 08:44:44 GMT, Andrew Haley <aph at openjdk.org> wrote:

> I'm trying to think of ways this might break.

Good, thanks! I came up empty where adding 64-bit paths in addition (and earlier on the lookup path) might actually be a problem.

> I'm not sure about "should be safe".

:) That comment was meant to be seen in the context of JDK 17/18. I agree for backporting I'd rather use the alternative patch as suggested in https://github.com/openjdk/jdk/pull/4657. Now, in the context of JDK 17 (and JDK 18) which has the SPARC port removed, it seems that simplification does make sense. It might not be 100% safe, I agree.

> I'm not an expert on Debian and
> Ubuntu, but AFAIK /usr/lib is the installed system's default arch,
> with multi-arch stuff like /usr/lib/i386-linux-gnu, etc. On such
> systems I believe that /usr/lib64 is often symlinked to point to
> /usr/lib, but it might not be: it wouldn't be completely insane to
> have some other arrangement. It could be argued that if the Debians
> want to violate the FHS it's on them to patch around it, but this
> patch is a change of behaviour, so it may not be entirely safe for
> back-porting.

Yes, agreed. Not safe for backporting.

-------------

PR: https://git.openjdk.java.net/jdk17/pull/200