Your message dated Tue, 11 Oct 2016 09:28:53 +0200
with message-id <5e82e83a-630b-5d5d-99d0-50fb22f19...@ubuntu.com>
and subject line Re: [Openjdk] Bug#828873: openjdk-8-jre-headless: inconsistent 
library installation paths
has caused the Debian Bug report #828873,
regarding openjdk-8-jre-headless: inconsistent library installation paths
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
828873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-8-jre-headless
Version: 8u91-b14-3
Severity: important

On i386, openjdk-8-jre-headless installs libraries to
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386(/server), consistently
using DEB_HOST_ARCH_CPU throughout.  On arm64, however, these libraries
wind up in /usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64(/server),
where arm64 corresponds to DEB_HOST_ARCH_CPU (as on i386) but aarch64
corresponds to DEB_HOST_GNU_CPU.  (On most other architectures, these
two variables are equivalent in practice.)

Presumably as a result of this discrepancy, gridengine FTBFS on arm64
due to looking in a nonexistent directory:

     [java]      [exec] cc -o jgdi_test -g  -DSGE_LOCK_DEBUG -L. -Wl,-z,relro 
-rdynamic -Wl,-rpath,\$ORIGIN/../../lib/lx-arm64  
-L/usr/lib/jvm/java-8-openjdk-arm64/jre/lib/arm64/server  jgdi_test.o -ljvm 
libuti.a libcommlists.a -lm -lpthread  
     [java]      [exec] ../libs/jgdi/Makefile:77: recipe for target 'jgdi_test' 
failed
     [java]      [exec] make[2]: Leaving directory 
'/«BUILDDIR»/gridengine-8.1.8+dfsg/source/LINUXARM64'
     [java]      [exec] not done
     [java]      [exec] /usr/bin/ld: cannot find -ljvm
     [java]      [exec] collect2: error: ld returned 1 exit status
     [java]      [exec] make[2]: *** [jgdi_test] Error 1

Could you please address this discrepancy, or explain to gridengine's
maintainers how to locate these libraries generically?

Thanks!

--- End Message ---
--- Begin Message ---
On 28.06.2016 20:47, Aaron M. Ucko wrote:
> "Aaron M. Ucko" <a...@alum.mit.edu> writes:
> 
>> On i386, openjdk-8-jre-headless installs libraries to
>> /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386(/server), consistently
>> using DEB_HOST_ARCH_CPU throughout.  On arm64, however, these libraries
>> wind up in /usr/lib/jvm/java-8-openjdk-arm64/jre/lib/aarch64(/server),
>> where arm64 corresponds to DEB_HOST_ARCH_CPU (as on i386) but aarch64
>> corresponds to DEB_HOST_GNU_CPU.  (On most other architectures, these
>> two variables are equivalent in practice.)
> 
> It looks like there's also a discrepancy on sparc64, on which both of
> those variables are set to sparc64, but the libraries wind up in
> /usr/lib/jvm/java-8-openjdk-sparc64/jre/lib/sparcv9 (and gridengine, for
> whatever reason, looks in
> /usr/lib/jvm/java-8-openjdk-sparc64/jre/lib/sparc).

the only consistency is to follow the upstream naming. See the jvm_archdir /
jvm_archpath macros in java_defaults.mk for these values.  If these are not up
to date, please report an issue for java-common.

Matthias

--- End Message ---

Reply via email to