I'm not recommending anything, I'm trying to help you verify whether
GCC's testsuite is failing because of testsuite bugs, gcc bugs, tools
bugs, or OS bugs. This should help you focus on the legitimate
problems with gcc.
In this case, the thousands of failures were an interaction between
how the testsuite runs the linker with -L paths relative to the
bootstrapped compiler in the local build directory, and wouldn't be
seen, typically, if you ran the testsuite against an installed compiler.
As a GCC developer and/or bleeding edge user, it's fairly common to
require a newer toolchain to support new features in gcc than is
being officially shipped by Apple. Running the testsuite successfully
counts as a "feature" in this case. In those cases, you can either
use binaries posted by members of Apple's compiler team, or build
odcctools from source. I don't see this as significantly different.
If your concern is that you don't trust the modifications that have
been made, you can view them and apply only the fixes you want:
<http://cvs.opendarwin.org/cgi-bin/cvsweb.cgi/projects/odcctools/src/>
Shantonu
On Jan 25, 2006, at 2:12 PM, Bradley Lucier wrote:
On Jan 23, 2006, at 8:07 PM, Shantonu Sen wrote:
I've posted a new version of odcctools (based on Apple's cctools
and ld64 source) which should fix a few thousand of the failures.
Instructions are at:
<http://www.opendarwin.org/projects/odcctools/usingodcctools.html>
This is based on cctools-590.18 and ld64-26.0.81, which should be
substantially similar to what you have, and since you can use --
prefix, you don't need to overwrite the Apple-provided tools.
Can you report how this changes things?
The results are much better, thanks:
http://gcc.gnu.org/ml/gcc-testresults/2006-01/msg01316.html
So what are you recommending people do? Use the OpenDarwin version
of cctools instead of relying on Apple's official version?
Brad
