This is an automatically filed bug for a failed rebuild attempt for GCC 4.3. http://fedoraproject.org/wiki/JesseKeating/gcc43MassRebuildProposal Please verify why this build failed and fix it. http://koji.fedoraproject.org/koji/taskinfo?taskID=451616 Exit code was 1, check the build.log for the failed buildArch task.
[ 59%] Building CXX object Utilities/DICOMParser/CMakeFiles/vtkDICOMParser.dir/DICOMAppHelper.o In file included from /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMParser.h:38, from /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMCallback.h:32, from /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.h:32, from /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:29: /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMFile.h: In static member function 'static uint DICOMFile::swap4(uint)': /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMFile.h:220: warning: suggest parentheses around arithmetic in operand of | /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMFile.h:221: warning: suggest parentheses around arithmetic in operand of | /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx: In member function 'virtual void DICOMAppHelper::ImagePositionPatientCallback(DICOMParser*, doublebyte, doublebyte, DICOMParser::VRTypes, unsigned char*, quadbyte)': /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:592: error: 'memcpy' was not declared in this scope /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:614: error: 'memcpy' was not declared in this scope /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx: In member function 'virtual void DICOMAppHelper::ImageOrientationPatientCallback(DICOMParser*, doublebyte, doublebyte, DICOMParser::VRTypes, unsigned char*, quadbyte)': /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:660: error: 'memcpy' was not declared in this scope /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:688: error: 'memcpy' was not declared in this scope /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx: In member function 'virtual void DICOMAppHelper::TransferSyntaxCallback(DICOMParser*, doublebyte, doublebyte, DICOMParser::VRTypes, unsigned char*, quadbyte)': /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:713: error: 'strcmp' was not declared in this scope /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx: In member function 'const char* DICOMAppHelper::TransferSyntaxUIDDescription(const char*)': /builddir/build/BUILD/VTK/Utilities/DICOMParser/DICOMAppHelper.cxx:1016: error: 'strcmp' was not declared in this scope make[2]: *** [Utilities/DICOMParser/CMakeFiles/vtkDICOMParser.dir/DICOMAppHelper.o] Error 1 make[1]: *** [Utilities/DICOMParser/CMakeFiles/vtkDICOMParser.dir/all] Error 2 make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.22987 (%build)
Looks like ACLs are closed for other Fedora developers: https://admin.fedoraproject.org/pkgdb/packages/name/vtk Axel, could you possibly open up the ACLs so that others can apply a patch and fix this? It is causing broken deps in rawhide: Broken deps for i386 ---------------------------------------------------------- <snip> vtk-examples-5.0.3-22.fc9.i386 requires vtkdata = 0:5.0.3 vtk-testing-5.0.3-22.fc9.i386 requires vtkdata = 0:5.0.3 Thanks.
Hi Alex, wouldn't you like to submit the patch for a review first?
*** Bug 440723 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Hi Alex, > > wouldn't you like to submit the patch for a review first? I thought that I might get time to do this, but unfortunately have not. It should be fairly straightforward, just search for each error in: http://gcc.gnu.org/gcc-4.3/porting_to.html and there's pretty much a straightforward fix. This should be fixed soon, however, as it it will cause issues on upgrade from F-8 as: F8-updates > F9 (0:5.0.4-19.fc8 > 0:5.0.3-22.fc9) as noted by Josh in recent post on fedora-devel-list In any case, it would be good to open up the ACLs so that others could patch it if you get busy. (I've opened up all my packages).
Looks like a new rebuild has arrived that applies a patch by Orion Poplawski on fedora-devel-list that fixes this: http://koji.fedoraproject.org/koji/buildinfo?buildID=45989 Once this has been tagged f9-final by rel-eng. I'll close this bug.
Apparently tagged now. Closing.
*** Bug 449426 has been marked as a duplicate of this bug. ***