This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: with_cross_host vs cross-hosted



> > + (@dfn{host}), and the machine that gcc will produce code for
> 
> GCC

Fixed (and the others).

> > + used to build the target libraries (like libstdc++).  If build and host
> 
> @code{libstdc++}

Changed, but why?  I'd expect @code{libstdc++.a} but libstdc++ is the
name of the package, not a file name or program.

> > + 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?

Libiberty, for example, is built twice.  The first time, host comes from
@option{--host} and the second time host comes from @option{--target}.
Historically, libiberty has not been built for the build machine,
though, which causes some interesting issues with programs used to
generate sources for the build.  Fixing this, so that libiberty is built
three times, has long been on the to-do list.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]