Bug#531917: marked as done (Breaks dh_nativejava package builds with default-jdk-builddep)
Your message dated Fri, 05 Jun 2009 21:34:00 +0000
with message-id <E1MCh32-00018e-04@ries.debian.org>
and subject line Bug#531917: fixed in java-gcj-compat 1.0.80-5
has caused the Debian Bug report #531917,
regarding Breaks dh_nativejava package builds with default-jdk-builddep
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 owner@bugs.debian.org
immediately.)
--
531917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531917
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: antlr
Version: 2.7.7-11
Severity: serious
X-Debbugs-CC: debian-gcc@lists.debian.org
From my pbuilder build log:
...
ln -s libantlr-java debian/libantlr-java-gcj/usr/share/doc/libantlr-java-gcj
dh_nativejava -plibantlr-java-gcj
make[1]: Entering directory `/tmp/buildd/antlr-2.7.7/debian/libantlr-java-gcj/usr/lib/gcj'
/usr/bin/gcj -c -fsource-filename=/tmp/filedNq7JM -g -O2 -fPIC -findirect-dispatch -fjni antlr.jar.1.jar -o antlr.jar.1.o
make[1]: /usr/bin/gcj: Command not found
make[1]: *** [antlr.jar.1.o] Error 127
make[1]: Leaving directory `/tmp/buildd/antlr-2.7.7/debian/libantlr-java-gcj/usr/lib/gcj'
aot-compile: error: /usr/bin/make exited with code 2
dh_nativejava: aot-compile returned exit code 1
make: *** [binary-arch] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
Other than adding gcj to the Build-Depends (which would tangle up the huge
mess of circular Build-Depends in Debian's Java packages even more), I
would have thought changing that line to:
dh_nativejava -plibantlr-java-gcj -- --gcj=/usr/bin/gcj-4.3 \
--dbtool=/usr/bin/gcj-dbtool-4.3
should also work, but it doesn't seem to pass along those arguments to
aot-compile. So I'm CCing the bug to the gcc-defaults (libgcj-common)
maintainers' list, to see if this is the intended behavior, and if this bug
is perhaps a more general problem that should be fixed in libgcj-common.
Maybe aot-compiler should be using the current default gcj-* instead of the
gcj symlink as its default.
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: java-gcj-compat
Source-Version: 1.0.80-5
We believe that the bug you reported is fixed in the latest version of
java-gcj-compat, which is due to be installed in the Debian FTP archive:
java-gcj-compat-dev_1.0.80-5_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat-dev_1.0.80-5_i386.deb
java-gcj-compat-headless_1.0.80-5_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat-headless_1.0.80-5_i386.deb
java-gcj-compat_1.0.80-5.diff.gz
to pool/main/j/java-gcj-compat/java-gcj-compat_1.0.80-5.diff.gz
java-gcj-compat_1.0.80-5.dsc
to pool/main/j/java-gcj-compat/java-gcj-compat_1.0.80-5.dsc
java-gcj-compat_1.0.80-5_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat_1.0.80-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 531917@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated java-gcj-compat package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 05 Jun 2009 12:57:11 -0700
Source: java-gcj-compat
Binary: java-gcj-compat-dev java-gcj-compat-headless java-gcj-compat
Architecture: source i386
Version: 1.0.80-5
Distribution: unstable
Urgency: low
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Description:
java-gcj-compat - Java runtime environment using GIJ
java-gcj-compat-dev - Java runtime environment with GCJ
java-gcj-compat-headless - Java runtime environment using GIJ (headless version)
Closes: 531917
Changes:
java-gcj-compat (1.0.80-5) unstable; urgency=low
.
* Depend on the unversioned gij/gcj packages. Closes: #531917.
Checksums-Sha1:
15b8f2934937d54eddec0afa8bd3632d4127db89 1320 java-gcj-compat_1.0.80-5.dsc
46230746f15d00ed6f68372b33bbe3d2d2a550e4 13112 java-gcj-compat_1.0.80-5.diff.gz
56d3a221c770b1a24b049ce84020679e926f16e2 2510 java-gcj-compat-dev_1.0.80-5_i386.deb
fc82adbb11795dbab627365cfcb38d780367389e 15240 java-gcj-compat-headless_1.0.80-5_i386.deb
614c749b4721e3fd07dd9b6558e631eb40f49a6b 1008 java-gcj-compat_1.0.80-5_i386.deb
Checksums-Sha256:
edb73a7ac1e19d95051af0c91d55c2f1f881de02fe2aa73055309fe3c1937501 1320 java-gcj-compat_1.0.80-5.dsc
2bdafbdb076d5f8d328842d7c783cb953b035f01f106cea9c4e5f2c0f947da44 13112 java-gcj-compat_1.0.80-5.diff.gz
e1222c00528a0531d9a7b0618e29370140e9ae7b6e6335a23236e960bdeb07be 2510 java-gcj-compat-dev_1.0.80-5_i386.deb
da288c811cd50c55ec33cf792abf329a345c8b5fd1ed8f53bf170fe9ab2cd242 15240 java-gcj-compat-headless_1.0.80-5_i386.deb
5bd7cbf131227a4dfd6b078e83fd0e2b0bb60f51561e86adf2076aa3842c7f3e 1008 java-gcj-compat_1.0.80-5_i386.deb
Files:
86a900efc28772960be4237612fb5f7c 1320 java optional java-gcj-compat_1.0.80-5.dsc
6af4a5579b208140d82924da3344368e 13112 java optional java-gcj-compat_1.0.80-5.diff.gz
ff06302370145ccea7d162058edf2bcf 2510 java optional java-gcj-compat-dev_1.0.80-5_i386.deb
cae0f309b704ac31810a85a5e2da98fa 15240 java optional java-gcj-compat-headless_1.0.80-5_i386.deb
99602cd09118134cf38c735fbae8648e 1008 java optional java-gcj-compat_1.0.80-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkopejoACgkQStlRaw+TLJwbkgCfd2z2xu2CtEOP239iFbvxrEy/
oGYAnjKEwEPZN/W4f4pKZUEsjzAAhuPF
=cKDo
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: