From owner-freebsd-ports@FreeBSD.ORG Fri Oct 11 23:24:47 2013 Return-Path: Delivered-To: freebsd-ports@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 ESMTP id DA3D7AB5 for ; Fri, 11 Oct 2013 23:24:47 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B0DA62B07 for ; Fri, 11 Oct 2013 23:24:47 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id ADFF537B54A; Fri, 11 Oct 2013 18:16:24 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3cxQ5g6NzDzkkm; Fri, 11 Oct 2013 18:16:23 -0500 (CDT) Date: Fri, 11 Oct 2013 18:16:23 -0500 From: "Matthew D. Fuller" To: Matthias Apitz Subject: Re: problems after installing ports-mgmt/portconf Message-ID: <20131011231623.GD59837@over-yonder.net> References: <20131011073713.GA12028@sh4-5.1blu.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131011073713.GA12028@sh4-5.1blu.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.21-fullermd.4 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.8 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-ports@freebsd.org 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: Fri, 11 Oct 2013 23:24:47 -0000 On Fri, Oct 11, 2013 at 09:37:13AM +0200 I heard the voice of Matthias Apitz, and lo! it spake thus: > > I have had to uninstall portconf again to be able to build more ports. Near's I can tell, portconf and bmake just flat out don't get along. With some squirreling around in make.conf, you can make _that_ warning shut up, but you just wind up with a different one for ports that you have portconf stuff for. I stopped investigating at that point :| -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.