Subject: Re: can't build
To: R.o.s.s H.a.r.v.e.y <ross@ghs.com>
From: Frederick Bruckman <fredb@immanent.net>
List: current-users
Date: 02/07/2002 18:52:56
On Thu, 7 Feb 2002, R.o.s.s  H.a.r.v.e.y wrote:

> If you just `setenv USETOOLS never', then all the direct invocations
> of make(1) will work the old way. This is the easiest way to just
> build to / or hack around in lower directories.

If alexander is intending to update to update his whole system (he
said "make build" didn't work), that would not be the right thing to
do at all.

> Alternatively, you can put, say, /usr/local/tools/bin in your
> path, alias `m' or something to nbmake-i386, and then run build.sh
> with -T /usr/local/tools. That's almost as convenient.
>
> > From: Frederick Bruckman <fredb@immanent.net>
> >
> > On Fri, 7 Feb 2003 alexander.spassov@textilmash.bg wrote:
> >
> > > "Makefile", Line 121: Mailformed conditional (${USETOOLS} == "yes")
> > > "Makefile", Line 121: Need an operator
> > > "Makefile", Line 123: if-less endif
> > > "Makefile", Line 123: Need an operator
> > > Fatal errors encountered -- cannot continue
> >
> > You're building on a new toolchain platform, but you don't have a new
> > toolchain. Read "BUILDING". Mainly, you'll just have to run "build.sh",
> > but you may want to look at the options first. Particularly, you may
> > want to set DESTDIR and TOOLDIR.

Frederick