Are you using 'make build'? If yes, what is your MKTOOLS settings?

You can always ./build.sh -T yourtooldir -t -m yourmachine, which
should build all tools as necessary.

David Laight wrote:
> I built 1.5ZC on a 1.5ZA system, then updated the system to 1.5ZC.
> The next build fails:
> 
> install ===> groff
> /usr/obj/tools/tools.NetBSD-1.5ZC-i386/bin/nbinstall -c -p -r -m 444 \
>     /usr/src/tools/groff/../../share/tmac/andoc \
>     /usr/obj/tools/tools.NetBSD-1.5ZC-i386/share/groff/tmac/tmac.andoc
> nbinstall: /usr/obj/tools/tools.NetBSD-1.5ZC-i386/share/groff/tmac: \
>     mkstemp: No such file or directory
> *** Error code 1
> 
> The problem seems to be that tools/tools.NetBSD-1.5ZC-i386 isn't
> repopulated properly.
> 
> The groff makefiles are far too convoluted for me to see what
> is actually meant to happen :-(
> 
> An 'rm -rf /usr/obj/tools/tools.NetBSD-1.5ZC-i386/lib/groff'
> gets past that failure, but a signifcant set of other
> tools including obj/tools/tools.NetBSD-1.5ZC-i386/bin/i386--netbsdelf-gcc
> do not get installed either.
> 
> I guess that deleting obj/tools/* with get around the problem, but it
> shouldn't be necessary.
> 
> I guess this can be simulated by deleteing tools.NetBSD-1.5ZC-i386...
> 
> 	David
> 
> -- 
> David Laight: david@l8s.co.uk
> 


-- 
Jaromir Dolecek <jdolecek@NetBSD.org> http://www.NetBSD.org/Ports/i386/ps2.html
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-