[MacPorts] #66283: compilers portgroup is not correctly testing for gcc_v

[MacPorts]

#66283: compilers portgroup is not correctly testing for gcc_v
---------------------------------+-----------------------
  Reporter:  ballapete           |      Owner:  (none)
      Type:  defect              |     Status:  new
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:  2.8.0
Resolution:                      |   Keywords:  tiger ppc
      Port:  boost176, boost171  |
---------------------------------+-----------------------

Comment (by kencu):

 Chris,

 The compilers PG seems to be doing something off at least with the boost
 ports. We noted it is always adding the RPATH on Tiger, which started
 this, but the issue is not with Tiger, but with the way it is finding the
 current gcc_version to see if RPATH should be added.

 On Mojave, testing with boost171, I added this to the compilers PG:

 {{{
 proc compilers::add_gcc_rpath_support {} {
     global prefix
     set gcc_v [compilers::get_current_gcc_version]
     if { ${gcc_v} >= 10 || ${gcc_v} == "devel" } {
 puts "adding RPATH, because gcc_v is:"
 puts ${gcc_v}
         configure.ldflags-delete  -Wl,-rpath,${prefix}/lib/libgcc
         configure.ldflags-append  -Wl,-rpath,${prefix}/lib/libgcc
     }
 }
 }}}

 and I see this, doing a "port info" with boost171:
 {{{
 $ port info
 adding RPATH, because gcc_v is:
 UNKNOWN
 adding RPATH, because gcc_v is:
 UNKNOWN
 boost171 @1.71.0_6 (devel)
 }}}

 I see the same on Tiger, where gcc is gcc7. The error shows up on Tiger
 because rpath is not supported there, but Tiger is not the cause of the
 issue.

-- 
Ticket URL: <https://trac.macports.org/ticket/66283#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS