Red Hat Bugzilla – Bug 434141
clearsilver failed massrebuild attempt for GCC 4.3
Last modified: 2013-01-09 21:57:54 EST
This is an automatically filed bug for a failed rebuild attempt for GCC 4.3.
Please verify why this build failed and fix it.
Exit code was 1, check the build.log for the failed buildArch task.
Errors in x86_64 Build.log
Processing files: clearsilver-0.10.5-2.fc9
error: File not found: /var/tmp/clearsilver-0.10.5-2.fc9-root-mockbuild/usr/bin/cs
error: File not found:
Clearsilver is very unhappy. -O0 and -O2 -fno-strict-aliasing do not make a
difference. Using gcc 3.4 doesn't resolve the issue.
Tried another build of clearsilver, but it still failed:
Proximate cause was missing files:
RPM build errors:
File not found: /var/tmp/clearsilver-0.10.5-3.fc9-root-mockbuild/usr/bin/cs
File not found: /var/tmp/clearsilver-0.10.5-3.fc9-root-mockbuild/usr/bin/cstest
Efficient cause appears to be that the cs and cstest binaries fail their
regression tests and (I guess) refuse to be installed:
Running cs regression tests
Failed Regression Test: test_crc.cs
See test_crc.cs.out and test_crc.cs.err
make: *** [test] Error 1
The test_crc.cs test fails on 64-bit machines because:
* ne_crc in util/neo_misc.c computes and UINT32
* _builtin_str_crc in cs/csparse.c stuffs this into a long int
* the testcase expects the UINT32 to be changed into a negative number by this
There are 3 possible fixes:
* disable the regression tests in cs/Makefile
* patch the test_crc.cs testcase to remove the offending test
* patch _builtin_str_crc to cast the number to int
We need a fix ASAP because this failure is causing broken deps.
Created attachment 302362 [details]
Patch for option 1
Created attachment 302364 [details]
Patch for option 2
Created attachment 302365 [details]
Patch for option 3
Pick one. :-)
If I don't get any other directions, I'll pick the second option ("patch the
test_crc.cs testcase to remove the offending test"), which I consider the least
Yay! It builds now:
Have you requested f9-final tagging from rel-eng already?
(In reply to comment #10)
> Have you requested f9-final tagging from rel-eng already?
(In reply to comment #11)
> (In reply to comment #10)
> > Have you requested f9-final tagging from rel-eng already?
Hmm, looking at:
Broken deps for i386
perl-clearsilver-0.10.4-5.fc8.i386 requires perl(:MODULE_COMPAT_5.8.8)
and noting that the build:
still doesn't have the f9-final tag, it looks like rel-eng either haven't tagged
it yet, or somehow missed the e-mail. I'll send another e-mail just to be sure.