This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 30 Aug 2001 15:05:59 -0300
- Cc: rittle at labs dot mot dot com, libstdc++ at gcc dot gnu dot org, ungaro at pegasus dot fmrp dot usp dot br, partain at dcs dot gla dot ac dot uk, ajhood at fl dot net dot au, Hermann dot Rochholz at faidor dot de, gcc-bugs at gcc dot gnu dot org, karl at gnu dot org, bkoz at gcc dot gnu dot org, rkl at connect dot org dot uk, apiszcz at mitre dot org
- Organization: GCC Team, Red Hat
- References: <200108242148.f7OLmBo78792@latour.rsch.comm.mot.com><ory9o7ouy9.fsf@feijoada.lsd.ic.unicamp.br><20010827130251.A8695@disaster.jaj.com>
On Aug 27, 2001, Phil Edwards <pedwards@disaster.jaj.com> wrote:
> That all makes sense. In my other message I was wondering why we do
> this all the time, and not (as the comments claim) only "if cross".
> For a native compile, shouldn't configuring for the host be the same as
> configuring for the target? I /know/ I'm missing somthing here.
We want to use the stage3 compiler to build the target libraries, even
if we the bootstrap compiler can generate code for the target (= host).
>> As for clobbering the source tree in order to test this stuff, you may
>> use symlink-tree to create a mirror of the source tree and then build
>> in it, so it won't affect the actual source tree.
> I could have sworn that the Makefiles do this already.
Only for target libraries, when building with srcdir=objdir.
--
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
- References:
- PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs