cvs commit: src Makefile.inc1

[Marcel Moolenaar]

On Wed, Jul 02, 2003 at 11:32:34PM +0300, Ruslan Ermilov wrote:
> On Wed, Jul 02, 2003 at 11:52:29AM -0700, Marcel Moolenaar wrote:
> > On Wed, Jul 02, 2003 at 12:39:10PM +0300, Ruslan Ermilov wrote:
> > > > if incompatible from the target. The compiler is now built
> > > > second and I'm expecting that all tools built after it will
> > > > not run. Unless something changed since the last time I looked.
> > > > 
> > > The cross-compiler is installed into WORLDTMP which is part of
> > > XPATH.  XPATH only appears in PATH for WMAKEENV and IMAKEENV.
> > 
> > Ok. I guess we dont need the cross-binutils in WORDTMP when we
> > build the cross-compiler. That was one of the original requirements.
> > 
> No we don't, we can't use it, it may be for a different arch.

Technically we can, provided we need to operate on the object files
for the target architecture. For example: if gcc needs to construct
libgcc2, which IIRC is the support library for use on the target,
it needs the cross-assembler provided by binutils.

It doesn't realy matter. If we currently don't need the cross tools
provided by binutils, we're ok. That's the point.

> Hmm, at least groff and config(8) use yacc(1) for building,
> and groff now comes before yacc.
> 
> I will re-test building of 5.x on 4.0-RELEASE to see if this
> change broke this, and report here.

Ok. I think yacc(1) is in the list for 3.x compatibility (yes,
the stuff is that old :-) Again, we may be ok now because we don't
try to upgrade from pre-4 installations, but that only means that
the ordering bugs go unnoticed.

An interesting test may be to clear the list of bootstrap-tools and
try to build world on 4.0. Add tools to fix build problems and
compare the resulting list with the one we have now. We may be able
to nuke some programs...

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel at xcllnt.net