Your message dated Tue, 14 May 2013 13:30:59 +0200
with message-id
<ca+7wusyw9rd28xe6vzygfoshit8qttc4sc9fopkcv8sldta...@mail.gmail.com>
and subject line FTBFS: byteswap.h:47: error: '__builtin_bswap32' was not
declared in this scope
has caused the Debian Bug report #707354,
regarding gdcm: FTBFS: byteswap.h:47: error: '__builtin_bswap32' was not
declared in this scope
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.)
--
707354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdcm
Version: 2.2.3-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> /usr/bin/cmake -E cmake_progress_report
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles
> [ 69%] Generating xml/vtkGDCMImageReader.xml
> cd /«PKGBUILDDIR»/obj-x86_64-linux-gnu/Utilities/VTK && /usr/bin/gccxml
> -fxml=/«PKGBUILDDIR»/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader.xml
> -fxml-start=_cable_ -I/usr/include/mummy-1.0.3 -I/usr/include/vtk-5.8
> -DCABLE_CONFIGURATION --gccxml-compiler /usr/bin/c++
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader_gccxml.cxx
> In file included from /usr/include/endian.h:60,
> from /usr/include/ctype.h:40,
> from /usr/include/c++/4.7/cctype:44,
> from /usr/include/c++/4.7/bits/localefwd.h:44,
> from /usr/include/c++/4.7/ios:42,
> from /usr/include/c++/4.7/ostream:40,
> from /usr/include/c++/4.7/iostream:40,
> from /usr/include/vtk-5.8/vtkIOStream.h:35,
> from /usr/include/vtk-5.8/vtkSystemIncludes.h:40,
> from /usr/include/vtk-5.8/vtkIndent.h:24,
> from /usr/include/vtk-5.8/vtkObjectBase.h:43,
> from /usr/include/vtk-5.8/vtkObject.h:41,
> from /usr/include/vtk-5.8/vtkAlgorithm.h:32,
> from /usr/include/vtk-5.8/vtkImageAlgorithm.h:28,
> from /usr/include/vtk-5.8/vtkImageReader2.h:29,
> from /usr/include/vtk-5.8/vtkMedicalImageReader2.h:26,
> from /«PKGBUILDDIR»/Utilities/VTK/vtkGDCMImageReader.h:67,
> from
> /«PKGBUILDDIR»/obj-x86_64-linux-gnu/Utilities/VTK/xml/vtkGDCMImageReader_gccxml.cxx:1:
> /usr/include/x86_64-linux-gnu/bits/byteswap.h: In function 'unsigned int
> __bswap_32(unsigned int)':
> /usr/include/x86_64-linux-gnu/bits/byteswap.h:47: error: '__builtin_bswap32'
> was not declared in this scope
> /usr/include/x86_64-linux-gnu/bits/byteswap.h: In function '__uint64_t
> __bswap_64(__uint64_t)':
> /usr/include/x86_64-linux-gnu/bits/byteswap.h:111: error: '__builtin_bswap64'
> was not declared in this scope
> make[3]: *** [Utilities/VTK/xml/vtkGDCMImageReader.xml] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2013/05/09/gdcm_2.2.3-1_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
reassign 707354 gccxml
found 707354 0.9.0+cvs20120420-4
fixed 707354 0.9.0+git20130511-1
thanks
I did a complete rebuild of gdcm within a sid chroot. I cannot
reproduce it. I am guessing this was due to gccxml. Hence reassigning.
Thanks.
--- End Message ---
