[MacPorts] #62298: beekeeper-studio @1.9.4: error: unrecognized command line option '-stdlib=libc++'

[MacPorts]

#62298: beekeeper-studio @1.9.4: error: unrecognized command line option
'-stdlib=libc++'
-------------------------------+--------------------
  Reporter:  cooljeanius       |      Owner:  (none)
      Type:  defect            |     Status:  new
  Priority:  Normal            |  Milestone:
 Component:  ports             |    Version:  2.6.4
Resolution:                    |   Keywords:
      Port:  beekeeper-studio  |
-------------------------------+--------------------

Comment (by ryandesign):

 Eric, this has the same origin as a previous ticket you filed: You have
 used `sudo port select gcc` to select a gcc, and this port incorrectly
 uses that selected gcc to build this port.

 Herby, you can see in the build log that this did not do what you wanted:

 {{{
 DEBUG: system -W /opt/local/var/macports/build
 /_opt_bblocal_var_buildworker_ports_build_ports_databases_beekeeper-studio
 /beekeeper-studio/work/beekeeper-studio-1.9.4:
 CSC_IDENTITY_AUTO_DISCOVERY=false yarn --frozen-lockfile
 }}}

 You should have been able to observe this on your system prior to
 committing.

 The variable `build.env` contains only what the portfile sets. MacPorts
 adds other variables to the environment internally; they are not reflected
 in `build.env`. If all of the environment variables that MacPorts sets are
 desired, as they usually are, then the port should not override the build
 phase; it should use the standard build phase normally instead.

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