Re: How about importing newer bmake?

[joerg%britannica.bec.de@localhost]

On Tue, May 30, 2006 at 10:05:38PM +0900, OBATA Akio wrote:
> On Tue, 30 May 2006 12:54:14 +0200, joerg%britannica.bec.de@localhost wrote:
> > As I said before, bootstrap/bootstrap explicitly calls boot-strap with
> > --with-default-sys-path. Instead of requesting the update please find
> > out why your platform is ignoring htat.
> 
> Because in devel/bmake/files/makefile.boot.in:
> =========================================================================
> MK=${prefix}/share/mk
> MKSRC=@mksrc@
> DEFAULT_MAKESYSPATH=/usr/share/mk:/usr/local/share/mk:/opt/share/mk
> ...
> BMAKE_ENV= CC="$(CC)" LIBC= MAKEFLAGS= 
> MAKESYSPATH=`pwd`/mk:${MKSRC}:${MK}:${DEFAULT_MAKESYSPATH}
> ...
> bootstrap:      bmake.boot .mk.done
>         ${BMAKE_ENV} ./bmake.boot -f Makefile
>         ${BMAKE_ENV} `pwd`/bmake -f Makefile test

To quote my Makefile from bootstrap/work:
CFLAGS+= -D_PATH_DEFSYSPATH=\"/usr/pkg/share/mk\"

makefile.boot is just used for the initial bootstrapping, the "real"
bmake should not have any reference to /usr/share/mk or whatever.

bmake test in bootstrap/work/DragonFly works here very well and it
didn't attempt to read /usr/share/mk/sys.mk.

Joerg