On Fri, 2018-01-26 at 09:52 +0000, Holger Kipp wrote:> Dear Scott,
>
> Am 26.01.2018 um 09:07 schrieb Scott Bennett <bennett at
sdf.orgbennett@sdf.org>>:
>
> cd /usr/src; PATH=/sbin:/bin:/usr/sbin:/usr/bin MAKE_CMD=make
/usr/obj/usr/src/make.amd64/bmake -m /usr/src/share/mk -f Makefile.inc1
TARGET=amd64 TARGET_ARCH=amd64 MK_META_MODE=no cleandir
> bmake: illegal argument to d option -- p
> usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
> [-d flags] [-E variable] [-f makefile] [-I directory]
> [-j max_jobs] [-m directory] [-V variable]
> [variable=value] [target ...]
> *** Error code 2
>
> Stop.
> make: stopped in /usr/src
> hellas# exit
> exit
>
> Script done on Fri Jan 26 01:33:18 2018
>
>
> ?????????????????????????????????Scott Bennett, Comm. ASMELG, CFIAG
>
> This sound similar to an issue with make in 2013:
>
> 20130613:
> Some people report the following error after the switch to bmake:
>
> make: illegal option -- J
> usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
> ...
> *** [buildworld] Error code 2
>
> this likely due to an old instance of make in
> ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
> which src/Makefile will use that blindly, if it exists, so if
> you see the above error:
>
> rm -rf `make -V MAKEPATH`
>
> should resolve it.
>
> Can you check if you have an older version of make in your makepath and
delete / rename it?
>
Yep, it's definitely running a bad old version of make, and the thought
that it's using /usr/obj/usr/src/make.amd64/bmake even though it's not
up to date fits the symptoms. ?I'm a bit confused by the "rm -rf"
command at the end... when I do make -V MAKEPATH I get nothing, so the
rm command would just be an error -- since that's from UPDATING in
2013, I'm thinking it may be out of date advice now.
I think the right fix here is probably "rm -rf /usr/obj/*" followed by
a make buildworld.
-- Ian