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: Patch checked in for K&R stage1 cc on obtabs.c


>BTW, isn't it time to make `make bootstrap' the default target, and
>require `make all' (or maybe `make onestage', so that `make all' could
>be equivalent to `make bootstrap') for a one-stage build?  This would
>allow `configure;make;make install' to ``just work''.  Of course this
>may break a lot of developers' scripts, but developers can easily
>handle this change, while users in general don't always figure out
>they need a different installation procedure for gcc.

Huzzah.  (Which means, I agree.  I've been thinking about the same
thing for awhile.)

In fact, as part of the configury/build rewrite, it'd be nice if
we could somehow have "make all" be the default as usual, and have
its dependencies look something like (pseudo-code):

  gcc: stage2/gcc
       ...

  stage2/gcc: stage1/gcc
       ...

  stage1/gcc: ...
       ...

Then, for people who want to short-circuit that, we could provide
them a configure-time option (*not* a build-time one) that'd do the
trick...somehow:

  CC=/usr/bin/cc ./configure --no-bootstrap ...

Or whatever.

The idea here is that restarting an aborted/crashed/interrupted build
shouldn't require special knowledge of where it stopped (no
"make bootstrap2" nonsense), among other things.

        tq vm, (burley)


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