[MacPorts] #71583: Multiple ports opportunistically use whatever they find in /usr/local

[MacPorts]

#71583: Multiple ports opportunistically use whatever they find in /usr/local
---------------------------+--------------------
  Reporter:  barracuda156  |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  base          |    Version:  2.10.5
Resolution:                |   Keywords:
      Port:                |
---------------------------+--------------------

Comment (by barracuda156):

 Replying to [comment:2 kencu]:
 > this kind of thing is why we insist on clean buildbot-built software to
 distribute.(eg why we can’t use someone’s gcc build to distribute via
 macports).
 >
 > by default, all compilers are configured to search /usr/local for
 headers and libs.
 >
 > the only compilers that do not do this, I believe, are macports-built
 gcc compilers, due to this:
 >
 > https://github.com/macports/macports-
 ports/blob/8ca160c32e0864ac8ce770389f206c30516d2fff/lang/gcc14/Portfile#L139
 >
 > and I’d have to check to make sure if that applies to every single
 macports gcc compiler

 It certainly has nothing to do with my gcc builds (sorry to disappoint
 here). Often the issue happens because some software hardcodes paths to
 search for libs, and not always it is noticed and fixed.
 This applies to 3 ports of mine, among some number of others’ ports (I
 will fix mine one now).

 I won’t bother checking the code of others’ ports to see whether Apple gcc
 is at fault or rather paths are hardcoded and not fixed.

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