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" <[email protected]> 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 M1 Garand is without doubt the finest implement of war > ever devised by man." > -- Gen. George S. Patton Jr. > > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to " > [email protected]" > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "[email protected]"
