This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Broken Canadian crosses
- To: Geoff Keating <geoffk at redhat dot com>
- Subject: Re: Broken Canadian crosses
- From: Michael Meissner <meissner at cygnus dot com>
- Date: Wed, 3 Jan 2001 22:09:00 -0500
- Cc: meissner at cygnus dot com, gcc at gcc dot gnu dot org
- References: <or4rzg69ja.fsf@guarana.lsd.ic.unicamp.br> <20010103104309.A16257@cse.cygnus.com> <200101040240.SAA06545@geoffk.org>
On Wed, Jan 03, 2001 at 06:40:56PM -0800, Geoff Keating wrote:
> > Date: Wed, 3 Jan 2001 10:43:09 -0500
> > From: Michael Meissner <meissner@cygnus.com>
> > Cc: gcc@gcc.gnu.org
> > Content-Disposition: inline
> > User-Agent: Mutt/1.2.5i
> >
> > (this was in response to a patch in gcc-patches, but I'm sending the response
> > to gcc instead)
> >
> > On Wed, Jan 03, 2001 at 11:38:01AM -0200, Alexandre Oliva wrote:
> > > They've been broken since Nov 23. Here's a patch that fixes them.
> > > I'm checking it in. There's no Copyright notice in build-make, so I'm
> > > not updating it. Should there be one?
> > >
> >
> > Geoff, would it be possible to add building a canadian cross to the auto build
> > mechanism? That way it would catch these things similar?
>
> You want me to try targetting gcc at the powerpc simulator? That
> sounds very hard.
Most of the problems occur in the classic canadian cross:
--build=<youros>
--target=powerpc-eabi
--host=i686-cygwin
You need to have a compiler tool chain:
--build=<youros>
--target=i686-cygwin
--host=<youros>
that was either freshly built/installed, or a frozen, blessed one. You don't
have to run the canadian cross, the point of the exercise is to make sure none
of the supporting mechanism was broken.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482