From owner-freebsd-ports@freebsd.org Wed Feb 3 15:03:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10914A99522 for ; Wed, 3 Feb 2016 15:03:51 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D9383D68 for ; Wed, 3 Feb 2016 15:03:50 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-244-25.knology.net [216.186.244.25] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u13F3mgE014512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 3 Feb 2016 09:03:49 -0600 Subject: Re: [moved from toolchain] GCC5: pkg vs. ports To: freebsd-ports@freebsd.org References: <56B20CA6.2080208@hiwaay.net> <56B215F4.1020905@infracaninophile.co.uk> From: "William A. Mahaffey III" Message-ID: <56B216D4.3060001@hiwaay.net> Date: Wed, 3 Feb 2016 09:09:18 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <56B215F4.1020905@infracaninophile.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2016 15:03:51 -0000 On 02/03/16 09:06, Matthew Seaman wrote: > On 2016/02/03 14:18, William A. Mahaffey III wrote: >> I just did a full 'pkg upgrade' on my FBSD 9.3R box, which installed the >> newest GCC5. I also updated ports. When I used the pkg-provided GCC5, it >> doesn't have graphite support enabled, so no auto-parallelization. When >> I checked the port w/ make showconfig. it shows graphite enabled. I am >> recompiling it as I write this, but I thought the pkg was/is configured >> from the port & would have graphite enabled by default, w/ no recompile >> needed on my part, no ? I have the various other pkg's req'd for >> graphite support pkg-installed (& just updated this A.M.), so I thought >> I was ready to go. Not a huge issue, but recompiling the compiler shoots >> about an hour on my box, would be sweet to avoid that. TIA for any clues >> & have a good one. > Unless you've your own poudriere setup, upgrading using binary packages > will always get you the default options for everything you install -- > what's in any ports tree or any option settings you have locally makes > no difference. > > If you are using poudriere, then remember to set options using > 'poudriere options -c some/package' -- it doesn't automatically pick up > options you make from the ports tree. > > Well, not unless you've been terribly cunning and done something like > creating a symbolic link like so: > > # cd /usr/local/etc/poudriere > # mv -f options options.old > # ln -s /var/db/ports options > > Cheers, > > Matthew Thanks, I am not running poudriere, I am only using ports for gcc5-devel to enable graphite support, everything else is pkg-maintained. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.