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: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Fri, 6 Jul 2001 08:25:00 +0100 (BST)
- cc: <pedwards at disaster dot jaj dot com>, <gcc-patches at gcc dot gnu dot org>
On Thu, 5 Jul 2001, DJ Delorie wrote:
> + (@dfn{host}), and the machine that gcc will produce code for
GCC
> + @code{--build=}, @code{--host=}, and @code{--target=}.
@option
> + configure may (and once did) assume that the host you specify is also
@code{configure} or @command{configure}
> + If build and host are the same, the gcc you are building will also be
GCC
> + used to build the target libraries (like libstdc++). If build and host
@code{libstdc++}
> + configured with @code{--target=foo-bar}, this compiler will be called
@option
> + @code{foo-bar-gcc}).
@command
> + machine you specified with @code{--target}. So, build is the machine
@option
> + Libiberty is built twice. The first time, host comes from @code{--host}
> + and the second time host comes from @code{--target}.
@option, @option, and perhaps you might want to address the longstanding
issue in the projects list of getting it built thrice, for build as well,
to avoid various kludges in the programs for the build system because they
can't use libiberty?
--
Joseph S. Myers
jsm28@cam.ac.uk