Date: Sat, 13 Apr 2013 23:20:49 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Garrett Cooper <yaneurabeya@gmail.com> Cc: freebsd-bugs@FreeBSD.org Subject: Re: conf/177845: WITH_BMAKE does not work on CURRENT Message-ID: <20130414062049.B0C8958097@chaos.jnpr.net> In-Reply-To: <866FF12C-2525-4A59-B20B-39A0522D7B44@gmail.com> References: <201304140420.r3E4K0Et063274@freefall.freebsd.org> <9B5C1BF8-17FB-4718-8AF1-3F8F5E55DAB8@gmail.com> <20130414054224.6720958097@chaos.jnpr.net> <866FF12C-2525-4A59-B20B-39A0522D7B44@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 13 Apr 2013 22:54:41 -0700, Garrett Cooper writes:
>The tree is synched up to the latest head version. I'm suspecting it =
>might be something to do with the changes made over the past 2 weeks in =
>terms of /Makefile, but I could be wrong. I'll look into this further =
>when I can..
I've just updated a tree to try to reproduce.
Are you sure /usr/bin/make is bmake?
I see lots of makefiles that invoke 'make' rather than ${MAKE},
so could imagine a problem if /usr/bin/make is *not* bmake.
If WITH_BMAKE is set, src/Makefile will build bmake and use it as
${MAKEPATH}/make, but the PATH is not tweaked to ensure that that 'make'
is found, so /usr/bin/make would get used.
Also of course one must do a parallel build, to trigger that error about
-J.
Anyway I started a parallel buildworld with /usr/bin/make not bmake
and the bug mentioned above not fixed to see if that causes the error
you see...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130414062049.B0C8958097>