nse@delfi-konsult.com wrote:

> > Is it really makewrapper in your log?
> I do not have any file by that name

You may have lines like this in build log:
---
cc  -O -o nbmake *.o  
#    objdir  /usr/obj.i386/tools
===> TOOLDIR path:     /usr/src/tooldir.NetBSD-4.0-i386
===> DESTDIR path:     /usr/src/destdir.i386
===> RELEASEDIR path:  /usr/src/releasedir
===> Created /usr/src/tooldir.NetBSD-4.0-i386/bin/nbmake
===> makewrapper:      /usr/src/tooldir.NetBSD-4.0-i386/bin/nbmake-i386
===> Updated /usr/src/tooldir.NetBSD-4.0-i386/bin/nbmake-i386
---

> > Isn't it "${TOOLDIR}/nbmake-macppc"?
> aaaahh... it is... and where could I find any description for this ?

In src/BUILDING?

Maybe it is not well explained because build.sh script
is recommended rather than using makewrapper directly
but distrib/cdrom is not designed to be supported by build.sh.
src/distrib/cdrom depends on third party software (mkisofs) and
will be superseded by "build.sh iso-image" once our makefs(8)
gets MacOS extension support on creating cd9660 fs.

> and still ... why is this not built by default?

It is. See the above log and src/build.sh around line 1073.

> cc -O -I. -I/usr/src/distrib/cdrom/macppc_installboot   -o  
> macppc_installboot installboot.lo cd9660.lo cd9660_util.lo
> cd9660.lo(.text+0x138): In function `cd9660_match':
> : undefined reference to `be16dec'

Hmm, maybe no one has tried this on big endian machines.
I'll take a look at it but may I ask again NetBSD version
of your compile host? Recent -current or other release?
---
Izumi Tsutsui