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

[MacPorts]

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

 * cc: essandess (added)


Comment:

 Replying to [comment:21 essandess]:
 > I'm updating port ghc and this annoying {{{libiconv}}} issue bites me
 every time.
 >
 > The simple solution is to run
 >
 > {{{
 > sudo port deactivate libiconv
 > }}}
 >
 > before running {{{sudo port test ghc}}}.
 >
 > My preferred solution would be to prevent linking to
 {{{/usr/lib/libiconv.dylib}}} in the first place. I don't see why this
 happens—{{{LIBRARY_PATH}}} is already set to {{{/opt/local/lib}}} in all
 MacPorts stages.
 >
 > Does anyone know how to tell MacPorts to build {{{ghc}}}  without using
 the system {{{iconv}}} library?

 Steve, please file a new ticket and attach logs showing what's happening
 so we can help you diagnose it.

 This ticket was about a problem mouse07410 experienced when trying to use
 a copy of ghc that had been compiled outside of MacPorts without MacPorts
 libiconv being present. This caused that ghc's static library to be
 compiled against the system's libiconv. Trying to link a program with that
 static library would fail if also trying to use MacPorts libiconv. The
 solution was to rebuild ghc from source while MacPorts libiconv was
 present. I would think that would already be the case when you build the
 MacPorts ghc port, so I don't think you're experiencing the same problem.
 This ticket asked us to change MacPorts libiconv to deviate from the
 intentions of its developers, and our response was that we would not do
 that. The resolution for your issue may be different.

 Replying to [comment:22 mouse07410]:
 > Are there any users of GHC port? Why

 As I [comment:19 explained before], ghc is an implementation of the
 haskell programming language, and we would like to offer haskell and all
 other programming languages in MacPorts, so that software that happens to
 be written in those programming languages can also be offered in MacPorts.
 It would not be convenient for MacPorts to have a policy that a program
 cannot be included in MacPorts only because that program happened to have
 been written in haskell.

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