[MacPorts] #57821: libiconv breaks compatibility with OS-provided

[MacPorts]

#57821: libiconv breaks compatibility with OS-provided
-------------------------+------------------------
  Reporter:  mouse07410  |      Owner:  ryandesign
      Type:  defect      |     Status:  reopened
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  libiconv    |
-------------------------+------------------------

Comment (by mouse07410):

 > The system libiconv and the version provided by the libiconv port are
 not 100% compatible even if the symbol renaming were turned off.
 \\
 I'm not sure I fully understand. If an app can be built against either
 library without modifying its source, then these two are compatible
 "enough"???
 \\

 \\
 > If your lib was built against the system libiconv, you need to use it
 with the system libiconv
 \\
 All I can say is "I'm trying, without much success so far..."  ;-) ;-(
 \\

 \\
 > If {{{-L/path/to -lfoo}}} is not working, try simply
 {{{/path/to/foo.dylib}}}.
 \\
 An excellent advice. I don't understand why this would work, while the
 {{{-L/some/thing}}} doesn't, but apparently it seemed to work! Thank you,
 Joshua!

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