Control: reopen -1 Control: reassign -1 src:gdcm On Tue, 03 Apr 2018 19:02:27 +0200 Gert Wollny <gw.foss...@gmail.com> wrote: > Control: forwarded -1 https://bugs.openjdk.java.net/browse/JDK-8200610 > > The bug is now visible upstream. but they closed it immediately. > Unfortunately I can't comment on the bug, because I am unable to > figure out how to open an account, but the suspected output path is > definitely writeable (after all compiling with an older openjdk version > works), so whatever is going on here, it must be something different. > > In addition: When I build the package with cowbuilder (arch:i386) it > fails, but when I then drop into a shell within cowbuilder, and then > run dpkg-buildpackage manually, the error doesn't occur any more. > > OTOH, when compiling the package directly on the host system (amd64) > the error is always reproducible, running e.g. > > javac -verbose -classpath /usr/share/java/vtk6.jar \ > vtkGDCMImageReader.java > > in the correct sub directory terminates with: > ---- > [wrote SimpleFileObject[/home/gerddie/Debian/debian-med/build- > area/gdcm-2.8.4/obj-x86_64-linux- > gnu/Utilities/VTK/java/vtk/vtkGDCMImageReader.class]] > [total 1308ms] > An exception has occurred > ... > --- > > The file vtkGDCMImageReader.class is written and has a non-zero size. > > Running javac with "strace -f" doesn't show any strange file access > close to the point when the exception is raised.
>From the upstream bug report: "cd /<<PKGBUILDDIR>>/obj-x86_64-linux-gnux32/Utilities/VTK/java && /usr/bin/javac -source 1.7 -target 1.7 -classpath /usr/share/java/vtk6.jar vtk/*.java While the log seems like it may be lacking info, there is not obviously a -d option in the command, meaning that javac will try and write the class file into the same directory as the source. If the source is coming from a source file in the jar file (vtk6.jar) then javac may try and write into the jar file, and therefore might get the observed exception." Did you check if adding a -d option to javac helps? BTW openjdk-9 is gone, this should be ported to openjdk 10 or 11, or preferably just use default-jdk. Cheers, Emilio
