This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: with_cross_host vs cross-hosted
- To: DJ Delorie <dj at redhat dot com>
- Subject: Re: with_cross_host vs cross-hosted
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 05 Jul 2001 22:23:55 -0300
- Cc: pedwards at disaster dot jaj dot com, gcc-patches at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200107051855.OAA14956@greed.delorie.com><20010705131509.A11597@nevyn.them.org><200107052038.QAA18219@greed.delorie.com> <jmsngb9gqf.fsf@geoffk.org><20010705192426.B19776@disaster.jaj.com><200107060030.UAA26811@greed.delorie.com>
On Jul 5, 2001, DJ Delorie <dj@redhat.com> wrote:
> + are build on (@dfn{build}), the machine that you are building for
^^^^^^^^^
typo
> + on the build at that time). If host and target are the same, but build
> + is different, you are using a cross-compiler to build a native for a
> + different system. Some people call this a @dfn{crossed native} or a
> + @dfn{cross-built native}
or host-x-host, right?
> + If build and host are the same, the gcc you are building will also be
> + used to build the target libraries (like libstdc++). If build and host
> + are different, you must have already build and installed a cross
> + compiler that will be used to build the target libraries (if you
> + configured with @code{--target=foo-bar}, this compiler will be called
> + @code{foo-bar-gcc}).
How about adding some information about cross builds here too, so that
we get fewer questions from people not having previously
built&installed binutils, or not having the target headers and
libraries around?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me