On Apr 13, 2013, at 11:20 PM, Simon J. Gerraty wrote: > > 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...
It's bmake: $ fmake -d A -f /dev/null 2>&1 | grep 'PARSEDIR = ' | wc -l 0 $ make -d A -f /dev/null 2>&1 | grep 'PARSEDIR = ' | wc -l 6 I'm rebuilding world right now so it might be due to a bug fixed in the past, but I swear I've seen this on another CURRENT box I kept reasonably (within the past couple months) up to date. Cheers, -Garrett _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"