[Debian-med-packaging] Bug#562387: Bug#562387: gdcm: FTBFS: cmake error

Thu Dec 24 13:38:57 UTC 2009

Package libvtk-java is *again* totally busted. This is total junk, and
I am getting fed up dealing with all bug in libvtk-java.
I am not adding a second patch in GDCM just for the debian system.

Here is what I have when using libvtk-java from unstable. Maitland, I
had to re-open 3 bugs after your upload. Could you please you
*actually* fix the issue and not add another new one !

Where is this jar file linking to: /usr/share/java/vtk.jar ?

$ ls -al /usr/share/java/vtk*
-rw-r--r-- 1 root root 17905 2009-11-16 12:35 /usr/share/java/vtkgdcm.jar
lrwxrwxrwx 1 root root    13 2009-12-24 14:25 /usr/share/java/vtk.jar
-> vtk-5.2.1.jar

/usr/share/java/vtk:
total 2940
drwxr-xr-x 2 root root    4096 2009-12-24 14:25 ./
drwxr-xr-x 5 root root    4096 2009-12-24 14:28 ../
-rw-r--r-- 1 root root 2995244 2009-12-14 06:38 vtk.jar

On Thu, Dec 24, 2009 at 11:43 AM, Lucas Nussbaum
<lucas at lucas-nussbaum.net> wrote:
> Source: gdcm
> Version: 2.0.14-2
> Severity: serious
> User: debian-qa at lists.debian.org
> Usertags: qa-ftbfs-20091213 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
>>  /usr/bin/fakeroot debian/rules clean
>> QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2
>> No patch removed
>> rm -rf .pc debian/stamp-patched
>> dh_testdir
>> dh_testroot
>> rm -f debian/configure*stamp debian/build*stamp
>> rm -rf debian/build*
>> dh_clean
>>  dpkg-source -b gdcm-2.0.14
>> dpkg-source: info: using source format `1.0'
>> dpkg-source: info: building gdcm using existing gdcm_2.0.14.orig.tar.gz
>> dpkg-source: info: building gdcm in gdcm_2.0.14-2.diff.gz
>> dpkg-source: info: building gdcm in gdcm_2.0.14-2.dsc
>>  debian/rules build
>> QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $? = 2
>> Applying patch poppler_breaks_api.patch
>> patching file Applications/Cxx/gdcminfo.cxx
>> patching file Applications/Cxx/CMakeLists.txt
>>
>> Applying patch cmake28_namelink.patch
>> patching file Source/DataDictionary/CMakeLists.txt
>> patching file Source/MediaStorageAndFileFormat/CMakeLists.txt
>> patching file Source/InformationObjectDefinition/CMakeLists.txt
>> patching file Source/Common/CMakeLists.txt
>> patching file Source/DataStructureAndEncodingDefinition/CMakeLists.txt
>> patching file Utilities/gdcmjpeg/12/CMakeLists.txt
>> patching file Utilities/gdcmjpeg/16/CMakeLists.txt
>> patching file Utilities/gdcmjpeg/8/CMakeLists.txt
>> patching file Utilities/VTK/CMakeLists.txt
>> patching file Utilities/gdcmcharls/CMakeLists.txt
>>
>> Now at patch cmake28_namelink.patch
>> touch debian/stamp-patched
>> dh_testdir
>> [ -d /build/user-gdcm_2.0.14-2-amd64-pU_tyG/gdcm-2.0.14/debian/build-python2.5 ] || mkdir /build/user-gdcm_2.0.14-2-amd64-pU_tyG/gdcm-2.0.14/debian/build-python2.5
>> cd /build/user-gdcm_2.0.14-2-amd64-pU_tyG/gdcm-2.0.14/debian/build-python2.5 && cmake /build/user-gdcm_2.0.14-2-amd64-pU_tyG/gdcm-2.0.14 -DCMAKE_INSTALL_PREFIX="/usr" \
>>               -DCMAKE_SKIP_RPATH=ON \
>>               -DGDCM_NO_EXECUTABLE_PROPERTIES=ON \
>>               -DCMAKE_VERBOSE_MAKEFILE= \
>>               -DGDCM_BUILD_APPLICATIONS=ON \
>>               -DGDCM_DOCUMENTATION:BOOL=ON \
>>               -DGDCM_PDF_DOCUMENTATION:BOOL=OFF \
>>               -DGDCM_BUILD_SHARED_LIBS=ON \
>>               -DGDCM_WRAP_PYTHON=ON \
>>               -DGDCM_WRAP_CSHARP=1 \
>>               -DGDCM_WRAP_JAVA=ON \
>>               -DGMCS_EXECUTABLE:FILEPATH=/usr/bin/csc \
>>               -DDESIRED_CSHARP_COMPILER_VERSION=2 \
>>               -DGDCM_BUILD_TESTING:BOOL=OFF \
>>               -DCMAKE_BUILD_TYPE:STRING=Release \
>>               -DGDCM_USE_SYSTEM_EXPAT:BOOL=ON \
>>               -DGDCM_USE_SYSTEM_UUID:BOOL=ON \
>>               -DGDCM_USE_SYSTEM_ZLIB:BOOL=ON \
>>               -DGDCM_USE_SYSTEM_OPENJPEG:BOOL=ON \
>>               -DGDCM_USE_SYSTEM_OPENSSL:BOOL=ON \
>>               -DGDCM_USE_SYSTEM_POPPLER:BOOL=ON \
>>               -DGDCM_VTK_JAVA_JAR:FILEPATH=/usr/share/java/vtk.jar \
>>               -DGDCM_USE_VTK:BOOL=ON
>> -- The C compiler identification is GNU
>> -- The CXX compiler identification is GNU
>> -- Check for working C compiler: /usr/bin/gcc
>> -- Check for working C compiler: /usr/bin/gcc -- works
>> -- Detecting C compiler ABI info
>> -- Detecting C compiler ABI info - done
>> -- Check for working CXX compiler: /usr/bin/c++
>> -- Check for working CXX compiler: /usr/bin/c++ -- works
>> -- Detecting CXX compiler ABI info
>> -- Detecting CXX compiler ABI info - done
>> -- Looking for stdint.h
>> -- Looking for stdint.h - found
>> -- Looking for inttypes.h
>> -- Looking for inttypes.h - found
>> -- Found POPPLER: /usr/lib/libpoppler.so
>> -- Found OPENJPEG: /usr/lib/libopenjpeg.so
>> -- Found ZLIB: /usr/lib/libz.so
>> -- Found OpenSSL: /usr/lib/libssl.so;/usr/lib/libcrypto.so
>> -- Found UUID: /usr/lib/libuuid.so
>> Will be using C# v2: /usr/bin/csc
>> -- Found EXPAT: /usr/lib/libexpat.so
>> -- Looking for pthread.h
>> -- Looking for pthread.h - found
>> -- Check if the system is big endian
>> -- Searching 16 bit integer
>> -- Looking for sys/types.h
>> -- Looking for sys/types.h - found
>> -- Looking for stdint.h
>> -- Looking for stdint.h - found
>> -- Looking for stddef.h
>> -- Looking for stddef.h - found
>> -- Check size of unsigned short
>> -- Check size of unsigned short - done
>> -- Using unsigned short
>> -- Check if the system is big endian - little endian
>> -- Found PythonLibs: /usr/lib/libpython2.5.so
>> -- Java version 1.6.0.0 configured successfully!
>> -- Found Java: /usr/lib/jvm/default-java/bin/java
>> -- Looking for stdlib.h
>> -- Looking for stdlib.h - found
>> -- Found Doxygen: /usr/bin/doxygen
>> -- Looking for include files HAVE_SYS_TIME_H
>> -- Looking for include files HAVE_SYS_TIME_H - found
>> -- Looking for include files HAVE_WINSOCK_H
>> -- Looking for include files HAVE_WINSOCK_H - not found.
>> -- Looking for include files HAVE_BYTESWAP_H
>> -- Looking for include files HAVE_BYTESWAP_H - found
>> -- Looking for rpc.h
>> -- Looking for rpc.h - not found
>> -- Looking for strcasecmp
>> -- Looking for strcasecmp - found
>> -- Looking for strncasecmp
>> -- Looking for strncasecmp - found
>> -- Looking for snprintf
>> -- Looking for snprintf - found
>> -- Looking for _stricmp
>> -- Looking for _stricmp - not found
>> -- Looking for _strnicmp
>> -- Looking for _strnicmp - not found
>> -- Looking for _snprintf
>> -- Looking for _snprintf - not found
>> -- Looking for gettimeofday
>> -- Looking for gettimeofday - found
>> You are using the SWIG version of VTKGDCM. This is not compatible with Activiz
>> -- Java version 1.6.0.0 configured successfully!
>> Implicitely adding debian package layout...
>> CMake Error at Utilities/VTK/CMakeLists.txt:268 (message):
>>   Could not find vtk.jar file, VTK_JAVA_JAR is wrong, please set proper
>>   GDCM_VTK_JAVA_JAR replacement var
>>
>>
>> -- Configuring incomplete, errors occurred!
>> make: *** [debian/configure-python2.5-stamp] Error 1
>
> The full build log is available from:
>   http://people.debian.org/~lucas/logs/2009/12/13/gdcm_2.0.14-2_lsid64.buildlog
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot.  Internet was not
> accessible from the build systems.
>
> --
> | Lucas Nussbaum
> | lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
> | jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |
>
>
>
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/debian-med-packaging
>

-- 
Mathieu