From owner-freebsd-current@FreeBSD.ORG Sat May 25 02:01:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87CCB328 for ; Sat, 25 May 2013 02:01:48 +0000 (UTC) (envelope-from jesse@glx.me) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 1E17018A for ; Sat, 25 May 2013 02:01:47 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id t59so3152517wes.16 for ; Fri, 24 May 2013 19:01:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=glx.me; s=g; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=4h/EhliLxss0dZ6lak3kzmz1uJQIvgpHRKcpsj7Z4dg=; b=Cr3+RN1QUZwnUGHlLkQ40GqYOPnUJLNkp78dXnZVD9Q31NLQ8NAn2NOHpipN0/WifC vuWz2Y9Y7U/b+wLzCJCpIEm6t2j366dlk5/Cj+d0wXicrtHFFLPmhTIS+6t8VDUj07eP A4fv/x3w6yWZzHhgox+ET+SyokjDUYZ7aFYcE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=4h/EhliLxss0dZ6lak3kzmz1uJQIvgpHRKcpsj7Z4dg=; b=nYFRexnIQdthbotjs3tyFJepPcmrDYdNYXmb0M1d4YRmNLyvVw8wJG76gOc8kYQaOH rgc8W40vxT2wXNwGtY2SH+hZydiwYCz/7HKG6d6FaMriThMwTHQgTK3CGTlIV9ReDpcw ktm111m+WnqYMhdbnuj2NPyjrRllLBiAtxSYtx/n0gFbgLXJclMzU457JvFayephy/44 oPyAhqvL2KubPJgANd9dNZnugXuzKs1bj3Podoc325pdkJg2gHFeuRH8ZV+JxAaKsYZI nv+ofyVtt3EPAmTrG6IvNmDq81Q+FO+s2zmv1Kv7VfFNB4fpoZ6qL6+8E8wWlVufSPBl 94+g== MIME-Version: 1.0 X-Received: by 10.180.37.109 with SMTP id x13mr1106991wij.20.1369447307008; Fri, 24 May 2013 19:01:47 -0700 (PDT) Received: by 10.194.14.168 with HTTP; Fri, 24 May 2013 19:01:46 -0700 (PDT) X-Originating-IP: [58.39.90.19] In-Reply-To: <20130524010315.GA83715@dragon.NUXI.org> References: <20130524010315.GA83715@dragon.NUXI.org> Date: Sat, 25 May 2013 02:01:46 +0000 Message-ID: Subject: Re: Unexpected behavior change [FreeBSD]make -> bmake From: "+a-#+3-d+c-v+:-.+@-=+w-x@s.a@d.e@e.k@x.y@g.h@h.i@p.q@k.m" To: obrien@freebsd.org, freebsd-current@freebsd.org X-Gm-Message-State: ALoCoQkLDYbFXt4rOtapyOxuJdqdEHpjjGrLoDZwhm4RJ0V86aj5/wDCivIlYjsRVXX4PWkyypUO Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 25 May 2013 02:01:48 -0000 Using bmake in ports instead of building it into base system. On Fri, May 24, 2013 at 1:03 AM, David O'Brien wrote: > For some reason bmake is now using share/mk/ from within a source tree > instead of the installation in /usr/share/mk/: > > /w/10/usr.bin/xinstall$ bmake > bmake: "/b/deo/10/share/mk/bsd.own.mk" line 444: MK_BMAKE can't be set > by a user. > > I believe this is against POLA as there is no guarantee that a share/mk/ > within the source tree is parseable by the invoked /usr/bin/bmake. It is > /usr/share/mk/ that is guaranteed to be consistent with /usr/bin/make. > > I see this as synonymous with using headers from lib/libc/ within the > source tree vs. /usr/include (which match the /lib/libc.so) when > building in this same way. I think we can all agree that is wrong > (the headers that match the libc that is being linked against needs > to be used). > > Can we go back to the pre-16-May-2013 behavior? > > -- > -- David (obrien@FreeBSD.org) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- (c) http://glx.me/