Bootstrap failure on powerpc-apple-darwin7.5.0

[Andrew Pinski]

On Oct 22, 2004, at 12:10 PM, Timothy J.Wood wrote:

>
>   I thought this patch got reverted (I must be thinking of something 
> else).
>
>   At any rate, no, I haven't done anything special to install an 
> updated cctools.  Is this even reasonable?  I'm building on Mac OS X 
> 10.3.5.  Apple's changes shouldn't break building on Apple's OS.  This 
> seems pretty clear to me, but make there is an argument to be made...?
>
>   I certainly have no interest in updating my cctools -- I need to use 
> this machine for 'real work' and I don't want to b0rk up my developer 
> tools install, preventing me from producing reliable and reproducible 
> builds of OS X 10.3 apps.  Forcing the install of a new assembler 
> seems unreasonable unless GCC 4.0 is dropping support for Mac OS X 
> 10.3 / Darwin 7.5  :)


The patch which was revert was the patch which checked to see if cctools
is up todate.

The reason why the new cctools is needed is because older versions of 
cctools
had a bug which makes some C++ code not to work correctly.  This is a
perfectly fine requirement if you want to use a new developmental 
version of
GCC which depends on cctools (which no longer includes dyld).

I do my GCC development on Darwin 7.4.1 and the cctools which Geoff 
posted
works just fine for me and can be considered stable and not a really
a developmental version at all.

Also I should note that for x86 Linux GCC is able to require a newer 
binutils
because of bugs in binutils so the point is that you should think of GCC
depending on versions of cctools/binutils and not as they are one 
package.

Thanks,
Andrew Pinski

PS I have nothing to do with the requirement, I am only a GCC developer
who follows darwin development closely.  (well I used to an intern at
Apple but I am not right now).