We saw some unexpected results, as documented in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=292629
at the end, in comments 44 - 46.
First, using build 334, we saw
FATAL: hudson.util.jna.GNUCLibrary (initialization failure)
java.lang.NoClassDefFoundError: hudson.util.jna.GNUCLibrary (initialization
failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:132)
at hudson.Util.createSymlink(Util.java:970)
Sounds like that's to be expected, given this bug.
But, the unexpected part, we then added
-Dhudson.Util.symlinkEscapeHatch=true
but got
FATAL: jnidispatch (/com/sun/jna/linux-ppc/libjnidispatch.so) not found in
resource path
java.lang.UnsatisfiedLinkError: jnidispatch
(/com/sun/jna/linux-ppc/libjnidispatch.so) not found in resource path
at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:700)
at com.sun.jna.Native.loadNativeLibrary(Native.java:680)
at com.sun.jna.Native.<clinit>(Native.java:108)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:194)
at hudson.util.jna.GNUCLibrary.<clinit>(GNUCLibrary.java:86)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:194)
at hudson.Util.createSymlink(Util.java:970)
This could easily be in our setup or install ... did not investigate.
Just wanted to document here that the workaround didn't work for us,
in case that's useful to you.
This was on Hudson 1.333