Re: Building without bootstrapping

2007-03-19 Thread Daniel Jacobowitz
On Mon, Mar 19, 2007 at 05:25:37AM -0700, Karthikeyan M wrote: > Thanks for the information. > So, if I want to debug a bug in the cc1 code that causes target > library build to fail - > should I just use the cc1 that is generated in /gcc/ ? Yes. -- Daniel Jacobowitz CodeSourcery

Re: Building without bootstrapping

2007-03-19 Thread Karthikeyan M
Thanks for the information. So, if I want to debug a bug in the cc1 code that causes target library build to fail - should I just use the cc1 that is generated in /gcc/ ? Is there a better way of doing this, without going through a make that builds some components successfully (cc1) and fails fo

Re: Building without bootstrapping

2007-03-18 Thread Brooks Moses
Kai Ruottu wrote: Paul Brook wrote: How can I get the build scripts to use the precompiled gcc throughout the build process ? Short answer is you can't. The newly build gcc is always used to build the target libraries. Nice statement but what does this really mean? Does this for ins

Re: Building without bootstrapping

2007-03-18 Thread Kai Ruottu
Paul Brook wrote: How can I get the build scripts to use the precompiled gcc throughout the build process ? Short answer is you can't. The newly build gcc is always used to build the target libraries. Nice statement but what does this really mean? Does this for instance mean that: "T

Re: Building without bootstrapping

2007-03-18 Thread Mike Stump
On Mar 18, 2007, at 2:55 PM, Karthikeyan M wrote: my problem is not yet solved It is, it doesn't bootstrap.

Re: Building without bootstrapping

2007-03-18 Thread Paul Brook
> How can I get the build scripts to use the precompiled gcc throughout > the build process ? Short answer is you can't. The newly build gcc is always used to build the target libraries[1]. Paul [1] Except when building a Canadian cross, in which case you're expected to have a build->target cr

Re: Building without bootstrapping

2007-03-18 Thread Karthikeyan M
Thanks for the help. But my problem is not yet solved I created a new folder , configured with --prefix= --disable-bootstrap --enable-languages=c option and then did a make but the newly built compiler is still used in the build process. i.e in the generated Makefile CC_FOR_TAR

Re: Building without bootstrapping

2007-03-16 Thread Mike Stump
On Mar 16, 2007, at 6:51 PM, Karthikeyan M wrote: when you run configure. If you do use --disable-bootstrap, just run "make all-gcc". I tried this, it is still using the compiled-compiler in stage2 and beyond There is no stage 2 if you aren't bootstrapping. I'd recommend rm - rf build a

Re: Building without bootstrapping

2007-03-16 Thread Karthikeyan M
when you run configure. If you do use --disable-bootstrap, just run "make all-gcc". I tried this, it is still using the compiled-compiler in stage2 and beyond I added some code to c-parser.c and this crashes the built-compiler when it tries to compile itself. I want the build to stop after s

Re: Building without bootstrapping

2007-03-16 Thread Ian Lance Taylor
"Karthikeyan M" <[EMAIL PROTECTED]> writes: > I am trying to build GCC without bootstrapping > > The config options I used were > > -- prefix= --disable-bootstrap --disable-libada --enable-languages=c > > I then did a > > make > > After that, I edited some code in c-parser.c , then, as sugges

Building without bootstrapping

2007-03-16 Thread Karthikeyan M
Hi , I am trying to build GCC without bootstrapping The config options I used were -- prefix= --disable-bootstrap --disable-libada --enable-languages=c I then did a make After that, I edited some code in c-parser.c , then, as suggested in http://gcc.gnu.org/ml/gcc/2007-02/msg00025.html , I t