[MacPorts] #56326: rev-upgrade considers gcc as broken due to libstdc++

[MacPorts]

#56326: rev-upgrade considers gcc as broken due to libstdc++
--------------------+--------------------
 Reporter:  raimue  |      Owner:  (none)
     Type:  defect  |     Status:  new
 Priority:  Normal  |  Milestone:
Component:  base    |    Version:  2.4.99
 Keywords:          |       Port:
--------------------+--------------------
 {{{
 ...
 --->  Found 1 broken file, matching files to ports
 gcc7 is using libstdc++ (this installation is configured to use libc++)
 gcc6 is using libstdc++ (this installation is configured to use libc++)
 --->  Found 3 broken ports, determining rebuild order
 DEBUG: Broken: pgAdmin3
 DEBUG: Broken: gcc7
 DEBUG: Broken: gcc6
 DEBUG: Processing port pgAdmin3 @0:1.22.2_0 +postgresql95
 DEBUG: Processing port gcc7 @2:7.3.0_0
 DEBUG: Processing port gcc6 @2:6.4.0_0
 --->  Rebuilding in order
      pgAdmin3 @1.22.2 +postgresql95
      gcc7 @7.3.0
      gcc6 @6.4.0
 ...
 }}}

 I was unable to find out why it thinks gcc6 and gcc7 are broken. I
 installed both gcc6 and gcc7 from the archives from packages.macports.org.
 Even stranger, if I deactive pgAdmin3, no broken files will be found and
 then, gcc6 and gcc7 are also no longer considered broken.

 Is this a problem with the gcc ports or with rev-upgrade reporting a
 false-positive? Why does it only appear when rev-upgrade finds at least
 one other broken port?

 pgAdmin3 apparently was not rev-bumped for the readline @7.0 update (looks
 like it copied the psql binary into the port), so this is a separate
 problem that needs to be dealt with. However, gcc6 and gcc7 should not be
 involved in this at all.

 I am attaching the full debug output.

-- 
Ticket URL: <https://trac.macports.org/ticket/56326>
MacPorts <https://www.macports.org/>
Ports system for macOS