This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
- From: Shantonu Sen <ssen at opendarwin dot org>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 16 Jan 2006 09:38:36 -0800
- Subject: Re: Status and rationale for toplevel bootstrap (was Re: Example of debugging GCC with toplevel bootstrap)
- References: <10601161739.AA12056@vlsi1.ultra.nyu.edu>
OK, so you want people to do
./configure --build=powerpc-foo-bar --host=powerpc-foo-bar --
target=powerpc64-foo-bar --prefix=$PWD/native64-compiler
make
make install
CC=$PWD/native64-compiler/bin/gcc /configure --build=powerpc64-foo-
bar --host=powerpc64-foo-bar --target=powerpc64-foo-bar
make <<implicitly bootstrap>>
rm -rf $PWD/native64-compiler
That would be really annoying for the same net effect, and something
better managed by GCC's build machinery
Shantonu
On Jan 16, 2006, at 9:39 AM, Richard Kenner wrote:
Just to be clear, you're suggesting that if you have:
--build=powerpc-foo-bar --host=powerpc64-foo-bar --
target=powerpc64-foo-bar
The user be able to specify something so that the build systems
knows
the build machine can execute the host binaries, and a 4-stage
bootstrap should occur?
Well, that's possible, but I'd really prefer to avoid dealing with
"bootstraps" of cross-compilers at all and stick to native
compilers, so
no, I'm not really suggesting that.