Date: Mon, 1 Feb 2016 10:52:15 -0553.75 From: "William A. Mahaffey III" <wam@hiwaay.net> Cc: FreeBSD toolchain mailing list !!!! <freebsd-toolchain@FreeBSD.org> Subject: Re: GCC5: pkg vs. ports Message-ID: <56AF8BF5.6030403@hiwaay.net> In-Reply-To: <56AF891B.9000607@FreeBSD.org> References: <56AF81BF.8050707@hiwaay.net> <CAKA3KycMNVAB4mzWCoOzt31TYPRjqnnEgZhmMwrcXPSGnsWwig@mail.gmail.com> <56AF8733.3010906@hiwaay.net> <56AF891B.9000607@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/16 10:40, Kubilay Kocak wrote: > On 2/02/2016 3:24 AM, William A. Mahaffey III wrote: >> On 02/01/16 10:18, Kubilay Kocak wrote: >>> Hi William, >>> >>> You may be seeing a previously saved config, try make rmconfig then >>> check again, or look at OPTIONS_DEFAULT inside Makefile >>> >>> You're correct, if graphite *is* a default option, the package should >>> have it . Only other thing I can think of is a silent graphite build >>> failure that isn't fatal, resulting in a built but incomplete package. >>> Unlikely all else being equal though >>> >>> Let us know what you find >>> >>> ./koobs >>> >>> On 2 Feb 2016 3:06 AM, "William A. Mahaffey III" <wam@hiwaay.net >>> <mailto:wam@hiwaay.net>> 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. >>> >>> >>> -- >>> William A. Mahaffey III >>> >> The *ports* version looks AOK, Makefile dated Jan 31, & 'make >> showconfig' says graphite is ready to go. When it gets done, I'll try to >> compile some code w/ it & verify it is AOK. I just didn't know why the >> *pkg* version was different. >> >> > William, > > I've just had a quick look, and if you're using the lang/gcc5 port, it > appears the GRAPHITE option defaults to OFF: > > https://svnweb.freebsd.org/ports/head/lang/gcc5/Makefile?revision=403073&view=markup#l48 > > This explains why that (gcc5) package doesn't have it enabled. > > Also see the last revision commit log: > > https://svnweb.freebsd.org/ports?view=revision&revision=403073 > > ./koobs > Actually, when I did a 'make install' from the '/usr/ports/lang/gcc5-devel' diredctory, the 1st thing it did was go download the files from kernel.org & proceed: Beginning background make install Initiated at 09:43:52 AM MCST on Monday, February 1, 2016 Making GCC 5.3.1.s20160126 for x86_64-portbld-freebsd9.3 [c,c++,objc,fortran,java] ===> License GPLv3 GPLv3RLE accepted by the user ===> Found saved configuration for gcc5-devel-5.2.1.s20151124 ===> gcc5-devel-5.3.1.s20160126 depends on file: /usr/local/sbin/pkg - found => gcc-5-20160126.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch http://mirrors.kernel.org/sources.redhat.com/gcc/snapshots/5-20160126/gcc-5-20160126.tar.bz2 gcc-5-20160126.tar.bz2 87 MB 0 Bps ===> Fetching all distfiles required by gcc5-devel-5.3.1.s20160126 for building ===> Extracting for gcc5-devel-5.3.1.s20160126 => SHA256 Checksum OK for gcc-5-20160126.tar.bz2. ===> Patching for gcc5-devel-5.3.1.s20160126 ===> Applying extra patch /usr/ports/lang/gcc5-devel/files/java-patch-hier ===> Applying FreeBSD patches for gcc5-devel-5.3.1.s20160126 ===> gcc5-devel-5.3.1.s20160126 depends on file: /usr/local/bin/as - found ===> gcc5-devel-5.3.1.s20160126 depends on executable: gmake - found ===> gcc5-devel-5.3.1.s20160126 depends on file: /usr/local/share/java/ecj-4.5.jar - found ===> gcc5-devel-5.3.1.s20160126 depends on executable: zip - found ===> gcc5-devel-5.3.1.s20160126 depends on file: /usr/local/bin/as - found ===> gcc5-devel-5.3.1.s20160126 depends on package: perl5>=5.20<5.21 - found ===> gcc5-devel-5.3.1.s20160126 depends on shared library: libgmp.so - found (/usr/local/lib/libgmp.so) ===> gcc5-devel-5.3.1.s20160126 depends on shared library: libmpfr.so - found (/usr/local/lib/libmpfr.so) ===> gcc5-devel-5.3.1.s20160126 depends on shared library: libmpc.so - found (/usr/local/lib/libmpc.so) ===> gcc5-devel-5.3.1.s20160126 depends on shared library: libiconv.so - found (/usr/local/lib/libiconv.so) ===> gcc5-devel-5.3.1.s20160126 depends on shared library: libisl.so - found (/usr/local/lib/libisl.so) ===> Configuring for gcc5-devel-5.3.1.s20160126 cd /usr/ports/lang/gcc5-devel/work/gcc-5-20160126 ; contrib/gcc_update --touch configure: loading site script /usr/ports/Templates/config.site When I look in /usr/ports/distfiles, I see: [root@devbox, gcc5-devel, 10:48:56am] 410 % lltr /usr/ports/distfiles/ total 617025 -rw-r--r-- 1 root wheel 1118845 Sep 23 2008 zip30.tar.gz -rw-r--r-- 1 root wheel 10658 Jun 17 2013 dialog4ports-0.1.5.tar.gz -rw-r--r-- 1 root wheel 1327342 Oct 5 2014 make-4.1.tar.bz2 -rw-r--r-- 1 root wheel 85807011 Oct 28 17:42 gcc-4.9-20151028.tar.bz2 -rw-r--r-- 1 root wheel 91322403 Nov 10 16:42 gcc-5-20151110.tar.bz2 -rw-r--r-- 1 root wheel 85841034 Nov 11 16:41 gcc-4.9-20151111.tar.bz2 -rw-r--r-- 1 root wheel 91330163 Nov 17 16:42 gcc-5-20151117.tar.bz2 -rw-r--r-- 1 root wheel 91309444 Nov 24 16:42 gcc-5-20151124.tar.bz2 -rw-r--r-- 1 root wheel 91342625 Dec 8 16:42 gcc-5-20151208.tar.bz2 -rw-r--r-- 1 root wheel 91345391 Jan 26 16:42 gcc-5-20160126.tar.bz2 [root@devbox, gcc5-devel, 10:48:57am] 410 % .... which is odd, I think, since I did a 'portsnap fetch update' this A.M. before I started .... I might have done that *after* the pkg upgrade, would that mess things up ? -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56AF8BF5.6030403>