From owner-freebsd-ports@FreeBSD.ORG Sat Jan 19 01:45:39 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 259F4D64 for ; Sat, 19 Jan 2013 01:45:39 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id D24D22C9 for ; Sat, 19 Jan 2013 01:45:38 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id BDDFD8A50F for ; Sat, 19 Jan 2013 01:45:37 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id r0J1jbhx045936 for ; Sat, 19 Jan 2013 01:45:37 GMT (envelope-from phk@phk.freebsd.dk) To: ports@freebsd.org Subject: Ports, bsd.lib.mk and NOPROFILE From: Poul-Henning Kamp Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 19 Jan 2013 01:45:37 +0000 Message-ID: <45933.1358559937@critter.freebsd.dk> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jan 2013 01:45:39 -0000 I just tried to build a system with -CURRENT from scratch, and it fell over in graphics/gd because NOPROFILE is now named NO_PROFILE in bsd.lib.mk grep(1) tells me that a number of other ports will also have this problem It may be appropriate with a bandaid in bsd.lib.mk, which emits a noisy warning, until all these ports are fixed. A good grep strategy is to look for files containing "NOPROFILE" and "bsd.lib.mk" but they need not be on the same line. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.