[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-questions
Subject:    Re: [toolchain] gcc5-devel question
From:       "William A. Mahaffey III" <wam () hiwaay ! net>
Date:       2015-12-23 15:36:01
Message-ID: 567AC4B3.8090108 () hiwaay ! net
[Download RAW message or body]

On 12/23/15 05:56, Gerald Pfeifer wrote:
> Hi William,
>
> On Thu, 10 Dec 2015, William A. Mahaffey III wrote:
>> However, pkg did reinstall gcc5-devel-5.2.1.s20151124 due to changed
>> options. I cd'ed to /usr/ports/lang/gcc5-devel & poked around a bit. I
>> saw no files or directories dated today, the latest was dated Dec 02,
>> the last time I upgraded & did a 'make install'. I did a find in
>> /usr/ports & /usr/ports/lang/gcc5-devel was all there was. Did the
>> compiler indeed get reinstalled ? If so, where :-) ?
> the location should not have changed, nor should have any packaging
> (additional files, say).


1st, thanks for your reply. This question was/is stupidly worded :-). 
What I was/am asking is whether the pkg-installed version of this 
compiler is compiled for Graphite support OOTB. The answer appears to be 
'no'. I just pkg-upgraded to the newest version & it is now called 5.3.1:

[29/33] Upgrading gcc5-devel from 5.2.1.s20151124 to 5.3.1.s20151208...
[29/33] Extracting gcc5-devel-5.3.1.s20151208: .......... done

However, when queried from the command line, it doesn't mention 'libisl' 
(req'd for Graphite support) & when I try to compile code using Graphite 
optimization (-floop-parallelize-all for me) it fails w/ an error 
message saying Graphite support not available:

f951: sorry, unimplemented: Graphite loop optimizations cannot be used 
(ISL is not available)(-fgraphite, -fgraphite-identity, -floop-block, 
-floop-interchange, -floo
p-strip-mine, -floop-parallelize-all, -floop-unroll-and-jam, and 
-ftree-loop-linear)

libisl is indeed available, pkg installed & ready to go. When I upgraded 
ports (portsnap fetch update) this A.M., nothing got upgraded, 
everything still dated 12/09 or earlier (when I last rebuilt it to turn 
on Graphite support, which apparently worked AOK) except for the log 
files from my compile. The port showed/shows Graphite enabled by default 
(I think). So, another question is whether the pkg & port have different 
build configurations ?


>
>> Also, when I did a 'make showconfig', it showed graphite support ready
>> to go (*yippeeee*, kudos), but no executable that I could locate on
>> short notice. Do I still need to compile it up, or is there an
>> executable ready to go somewhere not-so-obvious to me :-) ?
> Graphite support means additional optimizations GCC can perform (if
> you specify the respective options).
>
> You need to build the lang/gcc* ports that support Graphite with the
> respective option (GRAPHITE) enabled.  It is off by default, and thus
> not part of packages.
>
>> When I last compiled it up last week, I did a 'make install
>> FORCE_PKG_REGISTER=1' which overwrote /usr/local/bin/gcc5 (not a huge
>> issue, but still ....), how do I tell it to install the executable under
>> a different name ? BTW, I am *NOT* particularly familiar w/ the 'GNU
>> way', so pardon me if this is a bit noobish :-/ .... TIA & have a good
>> one.
> I am not aware of the FreeBSD packaging system supporting the renaming
> of individual files within a package.  You could try to install into a
> different location and then tweak things there, I guess.
>
> Gerald
>


-- 

	William A. Mahaffey III

  ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                            -- Gen. George S. Patton Jr.

_______________________________________________
freebsd-questions@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]