The problem is that last step: it takes a LONG time to build libjava,
for example. If I make a change that I need to give a sanity check to,
I want to compile GCC with it, but not all the other additional code: that's
for a later state in the development/testing cycle. Since building a stage
o
On Sat, Dec 30, 2006 at 12:30:06AM -0500, Richard Kenner wrote:
> > - Build supporting libraries for the build system tools
> > - Build supporting libraries for the host system tools
> > - Build gcc
> > - [NEW] Build libgcc
> > - If stage < final stage, go back to building some of the hos
> Would you feel OK if there were a make target to do a bootstrap
> without building the other target libraries?
Yes. That would only be a small increase in time (libiberty).
[EMAIL PROTECTED] (Richard Kenner) writes:
> > I don't believe anyone else considers this important.
>
> The history on this sort of thing is that people don't pay attention
> until it happens and then everybody starts yelling about bootstrap
> time increasing ...
>
> > - Build supporting lib
> I don't believe anyone else considers this important.
The history on this sort of thing is that people don't pay attention
until it happens and then everybody starts yelling about bootstrap
time increasing ...
> - Build supporting libraries for the build system tools
> - Build supporting l
On Fri, Dec 29, 2006 at 06:38:27PM -0500, Richard Kenner wrote:
> > You won't be able to do that any more. We've been saying that since
> > the first top level bootstrap rules went in, every time the subject
> > came up - this really shouldn't be a surprise.
>
> No, what's been said is that there
> You won't be able to do that any more. We've been saying that since
> the first top level bootstrap rules went in, every time the subject
> came up - this really shouldn't be a surprise.
No, what's been said is that there will be a MODE in which that can't
be done, but it was always claimed tha
On Fri, Dec 29, 2006 at 05:53:43PM -0500, Richard Kenner wrote:
> > Next week, after the merge, the bootstrap rules in the gcc directory
> > will go away.
>
> So what will be the way at that point to bootstrap JUST gcc?
You won't be able to do that any more. We've been saying that since
the fir
> Next week, after the merge, the bootstrap rules in the gcc directory
> will go away.
So what will be the way at that point to bootstrap JUST gcc?
As per the subject. The upcoming merge of toplevel libgcc will only
work either for disabled bootstrap, or with the toplevel bootstrap
mechanism. For this reason, we are now disabling "../configure
--disable-bootstrap && make bootstrap". The correct way to bootstrap is
to just use "./configu
10 matches
Mail list logo
