Date: Wed, 2 Apr 2014 21:15:44 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Warner Losh <imp@FreeBSD.org>, current@freebsd.org Subject: Re: make in dir Message-ID: <20140402181544.GS21331@kib.kiev.ua> In-Reply-To: <9A4DFA66-A2A3-45DB-9D18-422F9AE7095A@bsdimp.com> References: <20140402121504.GO21331@kib.kiev.ua> <9A4DFA66-A2A3-45DB-9D18-422F9AE7095A@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--pvGBTzZYFChjGQji
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 02, 2014 at 09:46:34AM -0600, Warner Losh wrote:
>=20
> On Apr 2, 2014, at 6:15 AM, Konstantin Belousov <kostikbel@gmail.com> wro=
te:
>=20
> > Hi,
> > it seems that recent changes to share/mk broke the ability to do anythi=
ng
> > in subdir of the source tree. As example, on the HEAD r264012 installed
> > yesterday:
> >=20
> > sandy% make /usr/home/pooma/build/bsd/DEV/src/tools/regressio=
n/kqueue
> > make: "/usr/share/mk/bsd.own.mk" line 436: MK_MAN can't be set by a use=
r.
>=20
> I was able to recreate this with ?make -m /blah-blah-blah -C tools/regres=
sion/kqueue clean?
> The important bit being -m. I have a fix that I?ll commit shortly.
>=20
> > Also, on stable/9 hosting the HEAD cross-env:
> > cd src && MAKEOBJDIRPREFIX=3D/usr/home/kostik/build/bsd/DEV/obj-amd64 D=
ESTDIR=3D/usr/home/kostik/build/bsd/DEV/netboot/sandy-amd64 SYSDIR=3D/usr/h=
ome/kostik/build/bsd/DEV/src/sys TARGET=3Damd64 make buildenv
> > Entering world for amd64:amd64
> > # cd share/mk
> > # make install
> > "bsd.own.mk", line 435: Malformed conditional (${.MAKE.LEVEL} =3D=3D 0)
> > "bsd.own.mk", line 436: MK_PROFILE can't be set by a user.
>=20
> This will happen with fmake. I?ve put some safety belts in place in anoth=
er fix
> to keep this from tripping people up (and plan on using a similar techniq=
ue
> to keep people from hitting the aicasm bug on such systems).
I noted that this is from stable/9-hosted buildenv. Shouldn't buildenv
mangle the path to select and possibly build bmake if needed ?
Anyway, your recent commits seems to fix my problems, thank you.
--pvGBTzZYFChjGQji
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)
iQIcBAEBAgAGBQJTPFPQAAoJEJDCuSvBvK1Bfy4P/iVES5AOSMqRf7PZKzbx8AYk
B7BXchXZZiw4RQg7z7gtv4vEsoLfFXgnAvDZlpuyU3xpl0TPYv9Na8mb9G1cVGaw
JF64us9PgZKzbYKUjXbHA7tbDZq4g9jbn/w6xueEjNI/g31Jv+qLnVifxaz/55GW
nh4anivrF9N1Q4JYsD4+212vCHSAk/gM8VfHjVJ5YPn9ebcMviUJe5ZZhCKboMiF
AqvYN8D+SKhZP7s21O/3SPk58KsIBWLC95TvaoFPzEuGBx+liL5DHQt/+Gma/PzH
Rjhs1YzxT2Dp8vhY+1stgImYjZ2naEPJh8dlccASN81/+vzCqsRUEHszyUR8yS/f
DputvfymTdcDKwnTLOSg4G41DJKNuvSoohWe+pfgva3aIP3p7Twn+d0qUbWuzDWB
73q5AoA33O0mF8ilGDc3WEC0L+U2SHkfbmj6P0duAxuLMz07+InVnJRQkuovCYBz
HD6LNL3eq3rAclnPqYboOS+JBJDzqEJB1WaOwroeidclpa1wmVQREkRAaq7GyVk5
e7Y56lhWa9DxCg+hgIwPaFZQltkHz1GajwB/CH3NRIwtiS1rGfsKz1wZ4xwqMRib
8cBOzA62oWBg+LzFj85D4LuW0NCFxy4PmCFJlrkAh/kqopMDbPYXpzJiEUrgjEgU
1ohXu6po5fVmGkdxvhdl
=iy+A
-----END PGP SIGNATURE-----
--pvGBTzZYFChjGQji--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140402181544.GS21331>