Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Doug Gregor
For the last few days I've been unable to make or bootstrap on i386-apple-darwin8.10.1. It doesn't seem to be a problem on my Core2-based Mac Pro, but on my Intel Core Duo (MacBook Pro) the build fails with the error message below. Perhaps we're trying to use Core2-only instructions on this platfo

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Benjamin Kosnik
>:8390:operands given don't match any known 386 instruction >:8491:operands given don't match any known 386 instruction >make[3]: *** [unwind-dw2_s.o] Error 1 >make[2]: *** [all-stage1-target-libgcc] Error 2 >make[1]: *** [stage1-bubble] Error 2 >make: *** [all] Error 2 You could configure with --

RE: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-02 Thread Jack Howarth
Doug, The fink packaging for gcc42/gcc43 builds fine on Macintel when we use... --with-arch=nocona --with-tune=generic --host=i686-apple-darwin8 to build either gcc 4.2.1 or gcc trunk. Jack

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-03 Thread Doug Gregor
On 10/2/07, Jack Howarth <[EMAIL PROTECTED]> wrote: > The fink packaging for gcc42/gcc43 builds fine on Macintel when we use... > > --with-arch=nocona --with-tune=generic --host=i686-apple-darwin8 This gets further, failing now for a very different reason: cc -O2 -g -O2 -m64 -O2 -O2 -g -O2

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-03 Thread Ian Lance Taylor
"Doug Gregor" <[EMAIL PROTECTED]> writes: > On 10/2/07, Jack Howarth <[EMAIL PROTECTED]> wrote: > > The fink packaging for gcc42/gcc43 builds fine on Macintel when we use... > > > > --with-arch=nocona --with-tune=generic --host=i686-apple-darwin8 > > This gets further, failing now for a very di

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-03 Thread Ian Lance Taylor
Ian Lance Taylor <[EMAIL PROTECTED]> writes: > "Doug Gregor" <[EMAIL PROTECTED]> writes: > > > On 10/2/07, Jack Howarth <[EMAIL PROTECTED]> wrote: > > > The fink packaging for gcc42/gcc43 builds fine on Macintel when we > > > use... > > > > > > --with-arch=nocona --with-tune=generic --host=i68

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-03 Thread Jack Howarth
Ian, Why should using a Canadian Cross suddenly break on Mac OS X? We have been using --host when building gcc packages in fink on Mac OS X for ages and it has never been a problem. I would think this should become a PR if gcc trunk has regressed on this issue. Jack ps For example, s

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-03 Thread Ian Lance Taylor
Jack Howarth <[EMAIL PROTECTED]> writes: >Why should using a Canadian Cross suddenly break on > Mac OS X? We have been using --host when building gcc > packages in fink on Mac OS X for ages and it has never > been a problem. I would think this should become a PR > if gcc trunk has regressed on

RE: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-04 Thread Dave Korn
On 04 October 2007 00:58, Ian Lance Taylor wrote: > Jack Howarth <[EMAIL PROTECTED]> writes: > >>Why should using a Canadian Cross suddenly break on >> Mac OS X? We have been using --host when building gcc >> packages in fink on Mac OS X for ages and it has never >> been a problem. I would th

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-04 Thread Ian Lance Taylor
"Dave Korn" <[EMAIL PROTECTED]> writes: > I always thought that if you want to build a "normal" package, i.e. one that > "will run on the machine on which you are doing the build" - what I've always > referred to as "a native build", you simply don't specify anything at all > (well, don't specif

Re: Make/bootstrap failure on i386-apple-darwin8.10.1 (Intel Core Duo)

2007-10-04 Thread Jack Howarth
Dave, Actually the usage of --host in the fink gcc packaging predates my ownership of it. I believe the fact that Apple configures their gcc builds with... --build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 ...may have been the motivator. This actually