This package failed to rebuild on x86_64 for FC4 Development around 2005-04-11 after an automated release bump. No build logs available afaics. Please request a rebuild.
I just noticed on fedora-extras-commits that Jeremy Katz beat me to it. I've been trying to find some time to get my x86_64 test box updated to rawhide to try a test build here, but I suppose now I may not have to.
So the build failed (again), but this time we have a build log. http://extras64.linux.duke.edu/failed/development/cone/0.64-3/x86_64/cone-0.64-3.failure.log Scanning quickly through the build log, the failures seem to be from missing files. Compiling maildirkeywords4.cpp In file included from /usr/lib/gcc/x86_64-redhat-linux/4.0.0/../../../../include /c++/4.0.0/bits/stl_tree.h:66, from /usr/lib/gcc/x86_64-redhat-linux/4.0.0/../../../../include /c++/4.0.0/set:65, from maildirkeywords.h:435, from maildirkeywords4.cpp:9: /usr/lib/gcc/x86_64-redhat-linux/4.0.0/../../../../include/c++/4.0.0/bits/stl_al gobase.h:64:28: error: bits/c++config.h: No such file or directory For a moment I thought perhaps cone.spec was missing an explicit BuildRequires: libstdc++-devel, but it is there, so I'm confused... I have my FC4t3/x86_64 test box up now, so I'll try a build there as soon as I get it updated to rawhide.
No, this is a known x86_64 build system problem. libstdc++-devel 32-bit and 64-bit replacing eachother. It has been discussed before, on extras-list most likely (I think related to "octave" build failure).
Ah, right, I remember that now. So is there a better workaround than to just keep re-submitting the build request until it succeeds?
I believe the trick is to not specify the redundant Buildrequires libstdc++-devel gcc-c++. With that, the build attempt did succeed: http://extras64.linux.duke.edu/needsign/4/cone/0.64-5/