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, see...
http://gcc.gnu.org/ml/gcc-testresults/2007-07/msg00847.html
On Wed, Oct 03, 2007 at 07:44:01AM -0700, Ian Lance Taylor wrote:
> 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=i686-apple-darwin8
>
> > > In file included from ../../../../mainlinegcc/libgcc/../gcc/libgcc2.c:65:
> > > ../../../../mainlinegcc/libgcc/../gcc/libgcc2.h:176: error: unknown
> > > machine mode 'libgcc_cmp_return'
> > > ../../../../mainlinegcc/libgcc/../gcc/libgcc2.h:177: error: unknown
> > > machine mode 'libgcc_shift_count'
> >
> > Support for those machine modes was added to mainline on July 6.
> >
> > The above command line suggests that you are building libgcc2 with cc,
> > though, rather than with the newly built compiler. That is unusual.
> > Are you doing a Canadian Cross (i.e., building with a cross compiler)?
> > How did you run configure?
>
> OK, so now I saw the --host option above.
>
> If you are not trying to do a Canadian Cross, then you should not use
> the --host option. Use the --build option instead. This is autoconf
> at work.
>
> Ian
