[MacPorts] #68026: rav1e @0.6.6: iconv linking fails, expecting symbols from MacOS's iconv lib

[MacPorts]

#68026: rav1e @0.6.6: iconv linking fails, expecting symbols from MacOS's iconv lib
---------------------+---------------------------------
  Reporter:  jgrg    |      Owner:  MarcusCalhoun-Lopez
      Type:  defect  |     Status:  assigned
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:
Resolution:          |   Keywords:
      Port:  rav1e   |
---------------------+---------------------------------

Comment (by ryandesign):

 Replying to [comment:3 kencu]:
 > This is an extremely common problem on MacPorts, and affects a great
 many builds that do not have perfect include and link lines.

 It's an extremely uncommon problem in MacPorts and elsewhere. It's very
 simple to get this right: use the iconv header and library from the same
 place. Do not mix and match. The problem only affects exceedingly weird
 software that's doing things very wrong.

 Replying to [comment:4 kencu]:
 > Another related issue is ports that use premade parts that are linked
 against the system libiconv, but then the build tries to link against
 MacPorts libiconv, and the two libiconv implementations are incompatible.
 This is currently affecting several ports as well (in the ghc/stack
 infrastructure), and has no great fix.

 ghc/stack is an example of exceedingly weird software doing things very
 wrong. It only goes wrong because they ship a static library that was
 linked against the system iconv and require everyone else to link with
 that static library and hilarity ensues. Static libraries are not
 recommended on macOS; this is an example of what happens when developers
 ignore Apple's recommendations.

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