Am 08.07.2014 14:13, schrieb Emmanuel Bourg: > Le 08/07/2014 11:47, Thomas Klute a écrit : > >> 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? > > Could this be related to Lintian emitting a > debug-file-with-no-debug-symbols warning about these files?
Possibly. Since the wheezy build fails in the dh_strip stage it doesn't get to lintian, but in the sid build log I see the linitan warnings, and during dh_strip there are many "debuglink section already exists" from objcopy. My current guess is that the OpenJDK build system already does something about the debug symbols, but I haven't looked into it yet. I'm not sure if it makes sense to with the alternative packaging going on. >> 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. > > Good idea, I merged it. I also got caught by this issue once. Thanks! I guess I'll have to see how that Launchpad repository develops. Will this bug continue to be updated? Kind regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
