[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#742864: Build without "nostrip" fails on weezy, another try for debian/control generation



Compiling on wheezy fails unless "nostrip" is set in DEB_BUILD_OPTIONS:

dh_strip -s  -Nopenjdk-8-8-jre-cacao -Nopenjdk-8-8-jre-jamvm  \
                -Xlibjvm.so --dbg-package=openjdk-8-dbg
objcopy:debian/openjdk-8-jdk/usr/lib/jvm/java-8-openjdk-amd64/bin/stEZfrnA:
cannot create debug link section
`debian/openjdk-8-dbg/usr/lib/debug/.build-id/27/b090842e021ced5bdfd3a9aba73af6b5afc44e.debug':
Invalid operation
dh_strip: objcopy --add-gnu-debuglink
debian/openjdk-8-dbg/usr/lib/debug/.build-id/27/b090842e021ced5bdfd3a9aba73af6b5afc44e.debug
debian/openjdk-8-jdk/usr/lib/jvm/java-8-openjdk-amd64/bin/javac returned
exit code 1
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2

Compiling with the same build system (plus freshly generated
debian/control) in a sid chroot works just fine. I'm not sure if this
should be considered important for OpenJDK 8 packaging (looks more like
a binutils bug to me). Any suggestions on how to handle this?

By the way, is the double "-8" in the cacao and jamvm package names
intentional? It seems strange to me.

I've also taken another look at the debian/control situation. My
previous suggestion to remove it from the repository could create the
problem that it could not easily be generated from a fresh repository
clone, because the code in debian/rules expected the file to be present
(though it could be empty). A patch available on my Github repository
[1] fixes that.

Kind regards,
Thomas

[1] https://github.com/airtower-luna/openjdk-8-debpkg


Reply to: