From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 18:25:06 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C11AB677 for ; Wed, 2 Apr 2014 18:25:06 +0000 (UTC) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9392E79D for ; Wed, 2 Apr 2014 18:25:06 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id kl14so572486pab.18 for ; Wed, 02 Apr 2014 11:25:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=w0EiDYRqiPxWKf8Jqjkxwt8vw+Hqi0jHCpAI5f53Jz8=; b=IPTHhe6hILmjN2HfiGcOjJLTbMagTw6UvnOxXyS4/X8qrOxb0oX445DHPaVsvEm62q DZXsX20lWTpUUX+6dF8jgDl3d9pU1eW5FF/HgZbk41UQ7N+kgBG9kjmQQrMLTRrYPda9 pGuFA//yEfMeI1gxcN8SO3wb2oTtyDnEh8Vb26uUpEXQH4LoYaOGFB2cVcHSZKFCiU+U PvOuvxu3kJyKzEYLe8GJ2j2UOVqwM777dq9CBSFgWUlh5KI/t6e1TNBY4F0Zq8EsxVBx 68rp1LVwp+wqpS1Xn9fUnfOhf27y4zkcUlHYhUEjkkF3ycHloj0Z8aqr8eRL/LGlm2f+ 9BrA== X-Gm-Message-State: ALoCoQnWkk8y+tUKMCssscPUHCSwKy/TcF+yUTGZzsvaM2tqUftCTeZOxPJYcR7i4n8IjATiCad4 X-Received: by 10.68.133.163 with SMTP id pd3mr1744399pbb.166.1396463100480; Wed, 02 Apr 2014 11:25:00 -0700 (PDT) Received: from [10.64.24.154] (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id g6sm13262164pat.2.2014.04.02.11.24.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Apr 2014 11:24:59 -0700 (PDT) Sender: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: make in dir From: Warner Losh In-Reply-To: <20140402181544.GS21331@kib.kiev.ua> Date: Wed, 2 Apr 2014 12:24:57 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <8010CB28-7BB1-4D6E-A4E0-975A6DB5A8D2@bsdimp.com> References: <20140402121504.GO21331@kib.kiev.ua> <9A4DFA66-A2A3-45DB-9D18-422F9AE7095A@bsdimp.com> <20140402181544.GS21331@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1874) Cc: Warner Losh , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 18:25:06 -0000 On Apr 2, 2014, at 12:15 PM, Konstantin Belousov = wrote: > On Wed, Apr 02, 2014 at 09:46:34AM -0600, Warner Losh wrote: >>=20 >> On Apr 2, 2014, at 6:15 AM, Konstantin Belousov = wrote: >>=20 >>> Hi, >>> it seems that recent changes to share/mk broke the ability to do = anything >>> 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/regression/kqueue >>> make: "/usr/share/mk/bsd.own.mk" line 436: MK_MAN can't be set by a = user. >>=20 >> I was able to recreate this with ?make -m /blah-blah-blah -C = tools/regression/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 = DESTDIR=3D/usr/home/kostik/build/bsd/DEV/netboot/sandy-amd64 = SYSDIR=3D/usr/home/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 = another fix >> to keep this from tripping people up (and plan on using a similar = technique >> 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 ? Yea, I would have thought so... > Anyway, your recent commits seems to fix my problems, thank you. You are welcome. Don=92t hesitate to give a yell if you discover other problems=85 Warner