Your message dated Wed, 19 Nov 2014 19:17:56 +0100 with message-id <20141119181754.ga19...@ugent.be> and subject line Re: Bug#769693: Please giveback libjogl2-java has caused the Debian Bug report #769693, regarding libjogl2-java: FTBFS on arm64 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.) -- 769693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libjogl2-java Version: 2.2.4+dfsg-1 Severity: serious Your package FTBFS on arm64, ppc64el and s390x. Below is an excerpt from the arm64 build log Property "nativewindow_x11.useLibJAWT" has not been set [echo] nativewindow_x11.useLibJAWT ${nativewindow_x11.useLibJAWT} [echo] Compiling nativewindow_x11 [echo] java.lib.dir.platform: /usr/lib/jvm/java-7-openjdk-arm64/jre/../jre/lib/aarch64 [cc] 4 total files to be compiled. [cc] gcc -include /usr/share/gluegen2/make/stub_includes/platform/glibc-compat-symbols.h -c -fno-rtti -fPIC -D__unix__ -D__X11__ -DNDEBUG -I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native -I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11 -I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11 -I/«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native -I/usr/lib/jvm/java-7-openjdk-arm64/include -I/usr/lib/jvm/java-7-openjdk-arm64/include/linux -I/usr/share/gluegen2/make/stub_includes/platform /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/NativewindowCommon.c /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11/Xmisc.c /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/src/nativewindow/native/x11/XineramaHelper.c [cc] cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [cc] cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [cc] cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [cc] /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c: In function 'Java_jogamp_nativewindow_x11_X11Lib_XSynchronize__JZ': [cc] /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/build/nativewindow/gensrc/native/X11/X11Lib_JNI.c:257:8: warning: assignment makes integer from pointer without a cast [cc] _res = XSynchronize((Display *) (intptr_t) display, (Bool) onoff); [cc] ^ [cc] cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [cc] Starting link [cc] gcc -static-libgcc -shared -o libnativewindow_x11.so NativewindowCommon.o Xmisc.o X11Lib_JNI.o XineramaHelper.o -lX11 -lXxf86vm -lXrender [cc] /usr/bin/ld: libnativewindow_x11.so: No symbol version section for versioned symbol `memcpy@GLIBC_2.0' [cc] /usr/bin/ld: final link failed: Nonrepresentable section on output [cc] collect2: error: ld returned 1 exit status [ant] Exiting /«BUILDDIR»/libjogl2-java-2.2.4+dfsg/make/build-nativewindow.xml. BUILD FAILED The other two look much the same This seems like some kind of screwup related to specifying a specific and old symbol version that doesn't exist on more recent ports but i'm not an expert.
--- End Message ---
--- Begin Message ---Hi, On Tue, Nov 18, 2014 at 05:40:26PM +0100, gregor herrmann wrote: > > Hmmm... I installed the build-deps into an arm64 sid chroot on asachi > > (arm64 porterbox) to take a look, but it seems to build okay now. > > Am I missing something, or can we try to run this through the buildd again? > > Hmmm … do we have an idea why it failed twice (on two separate > machines) on 2014-11-15 and why it passes now an a third one? > > I guess the buildd people would be interesting in the reasons for yet > another giveback :) This time it built fine on the same buildd as last time. I'm not sure what changed... Cheers, Ivo
--- End Message ---
