But for some reason nbmakeinfo is not being used and that would be because
some configure scripts are looking specifically for makeinfo rather than
nbmakeinfo.

Most configure scripts in the toolchain default MAKEINFO to makeinfo
rather than nbmakeinfo.

If you examine the makefiles created by the toolchain you see they include
the following:

MAKEINFO = `if [ -f $$r/texinfo/makeinfo/Makefile ] ; \
        then echo $$r/texinfo/makeinfo/makeinfo ; \
        else echo makeinfo ; fi`

If the tools makeinfo is installed as "nbmakeinfo" how is this makefile
going to know that? $$r does not evalute to /usr/src/tools, but rather
/usr/src/tools/toolchain/${OBJDIR}/build and texinfo doesn't exist there.

All of this was learned by running on an i386 pc running NetBSD1.5Y with
-current sources from 2002-01-10:
(cd /usr/src && ./build.sh -m i386 -T$TOOLDIR -t )

On Sat, 12 Jan 2002, gabriel rosenkoetter wrote:

> Date: Sat, 12 Jan 2002 18:28:06 -0500
> From: gabriel rosenkoetter <gr@eclipsed.net>
> To: current-users@netbsd.org
> Subject: Re: build.sh error on current
>
> On Sat, Jan 12, 2002 at 05:58:16PM +0100, Julio Merino wrote:
> > I meant the text series of the installation. I know it is in the source
> > tree but I guess that it should be built before it is used. Is this a
> > bug? I think that the build of toolchain should also build this, as it
> > is used to "compile" several programs later.
>
> makeinfo is part of the toolchain.
>
> There aren't quite enough details in Dan's report (and the text is
> just a touch difficult to read; Dan, in the future, could you avoid
> the random line breaks?) to be sure what's wrong.
>
> At the least, the toolchain makeinfo is called nbmakeinfo (should be
> at ${TOOLDIR}/bin/nbmakeinfo). If there's a Makefile trying to exec
> it as makeinfo, there's an error in that Makefile.
>
> --
> gabriel rosenkoetter
> gr@eclipsed.net
>

Elfin