Package: dcmtk
Version: 3.5.3-4
Severity: important

Hi,
your package has been requeued for a binaryNMU (probably because it was
built previously with wrong libraries) on m68k and failed to build, even
though the same source built fine on m68k on Oct 3, 2005, no holidays for
buildds...

Automatic build of dcmtk_3.5.3-4.0.1 on aahz by sbuild/m68k 69
[...]
Checking correctness of source dependencies...
Toolchain package versions: libc6-dev_2.3.5-6 
linux-kernel-headers_2.6.13+0rc3-1.1 gcc-4.0_4.0.2-2 g++-4.0_4.0.2-2 
binutils_2.16.1-3 libstdc++6-4.0-dev_4.0.2-2 libstdc++6_4.0.2-2
[...]
make[3]: Entering directory `/build/buildd/dcmtk-3.5.3/dcmsign/libsrc'
c++     -DHAVE_CONFIG_H  -DNDEBUG  -c -I. -I. -I../include 
-I../../config/include -I../../ofstd/include -I../../dcmdata/include  \
         -fPIC -O2 -I/usr/include/libxml2 -D_REENTRANT -D_XOPEN_SOURCE_EXTENDED 
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_BSD_COMPAT -D_OSF_SOURCE 
-D_POSIX_C_SOURCE=199506L -Wall  dcsignat.cc
c++     -DHAVE_CONFIG_H  -DNDEBUG  -c -I. -I. -I../include 
-I../../config/include -I../../ofstd/include -I../../dcmdata/include  \
         -fPIC -O2 -I/usr/include/libxml2 -D_REENTRANT -D_XOPEN_SOURCE_EXTENDED 
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -D_BSD_COMPAT -D_OSF_SOURCE 
-D_POSIX_C_SOURCE=199506L -Wall  sicert.cc
sicert.cc: In member function 'OFCondition SiCertificate::read(DcmItem&)':
sicert.cc:170: error: invalid conversion from 'Uint8**' to 'const unsigned 
char**'
sicert.cc:170: error:   initializing argument 2 of 'X509* d2i_X509(X509**, 
const unsigned char**, long int)'
make[3]: *** [sicert.o] Error 1

See full logs at:
http://buildd.debian.org/build.php?arch=m68k&pkg=dcmtk

You will notice that the successful build used slightly different versions
of gcc, libc, binutils:

Toolchain package versions: libc6-dev_2.3.5-4 linux-kernel-headers_2.6.12.0-1 
gcc-4.0_4.0.1-8.0.1 g++-4.0_4.0.1-4 binutils_2.16.1-2 
libstdc++6-4.0-dev_4.0.1-4 libstdc++6_4.0.1-4

So I am suspecting either a bug in gcc, or a bug in your package, which uses
illegal c++ code that only gets detected in gcc 4.0.2. BTW to rule out a
problem in the m68k gcc, I just tried to build the package in an unstable
chroot on my AthlonXP box, and it failed at exactly the same place, so I
think the bug is in your package.

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to