[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 kencu):

 Replying to [comment:9 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.

 Oh, I don't know, Ryan -- it looks a lot more common than you suggest. I
 believe it is the single most-commonly reported issue with macports.

 I didn't read all of these in endless detail, but It took me about 10
 minutes to find about 40 quick examples where simply having a libiconv
 port caused a build failure that stopped someone long enough that it led
 them to post about it, and that doesn't even include all of macports
 tickets about it. For most of these issues, the upstream solution is to
 "uninstall libiconv".  They don't all look like bizarro build systems or
 ghc idiosyncracies.

 They are build issues, sure. They can be addressed and fixed by people who
 understand such things. I can fix almost all of them of course, for
 example. They all take someone's time, however, trip up builds, tie people
 down, and ... induce some people to uninstall macports.

 I think the question really is how much benefit does having a libiconv
 port add to macports, vs how much of a headache is it? The system
 lilbiconv seems just fine on all the macos systems macports installs on,
 in particular all newer systems. The system software  is all linked to the
 system libiconv, so even if you install a newer one via macports you
 haven't avoided perils of the old one.

 http://archive.ambermd.org/201007/0130.html

 http://blog.omega-prime.co.uk/2011/01/28/solving-ghc-iconv-problems-on-
 os-x-10-6/

 http://cegui.org/forum/viewtopic.php?t=7565

 http://qdpl.blogspot.com/2010/08/macrails-dyld-lazy-symbol-binding.html

 https://apple.stackexchange.com/questions/448063/macos-symbol-not-found-
 libiconv-when-run-sudo-command

 https://apple.stackexchange.com/questions/69936/terminal-and-bash-cant-
 start-with-libiconv-error

 https://copyprogramming.com/howto/libiconv-or-iconv-undefined-symbol-on-
 mac-osx

 https://discourse.slicer.org/t/build-problem-unknown-libiconv-symbols-on-
 macos-using-macports/1796

 https://ffmpeg.org/pipermail/ffmpeg-devel/2013-March/139915.html

 https://github.com/kbknapp/cargo-outdated/issues/187

 https://github.com/kbknapp/cargo-outdated/issues/256

 https://github.com/OpenModelica/OpenModelica/issues/10944

 https://github.com/rabiaasif/git-osx-installer/issues/18

 https://github.com/rust-lang/git2-rs/issues/180

 https://github.com/rust-lang/git2-rs/issues/263

 https://gitlab.haskell.org/ghc/ghc/-/issues/18743

 https://gitlab.haskell.org/ghc/ghc/-/issues/22118

 https://gitlab.kitware.com/cmake/cmake/-/issues/18892

 https://itecnote.com/tecnote/macos-how-to-fix-libiconv-error-on-mac/

 https://jongampark.wordpress.com/2014/01/30/libiconv-from-macport-and-
 os-x-framework/

 https://lightrun.com/answers/rikvdkleij-intellij-haskell-fails-to-install-
 haskell-tools-because-its-using-the-wrong-compiler

 https://mailman.speech.sri.com/pipermail/srilm-user/2014q2/001665.html

 https://mattgumbley.wordpress.com/2021/06/21/rust-instrumentation-on-
 macos-in-the-presence-of-macports/

 https://mw.gl/posts/libiconv_mac/

 https://nostandardwork.com/tag/git/

 https://sourceforge.net/p/fontforge/mailman/message/36910268/

 https://stackoverflow.com/questions/1148450/unable-to-build-scipy-on-
 os-x-10-5-7

 https://stackoverflow.com/questions/12619600/libiconv-and-macos

 https://stackoverflow.com/questions/13059273/libiconv-2-dylib-not-found

 https://stackoverflow.com/questions/13301786/how-to-fix-libiconv-error-on-
 mac

 https://stackoverflow.com/questions/27392085/cant-link-to-iconv-on-os-x

 https://stackoverflow.com/questions/38880007/cant-compile-gdal-on-
 osx-1-11-6-due-to-libiconv-link-error

 https://stackoverflow.com/questions/43359289/architecture-x86-64-while-
 running-haskell-code-haskell-osx-iconv

 https://stackoverflow.com/questions/57734434/libiconv-or-iconv-undefined-
 symbol-on-mac-osx

 https://stackoverflow.com/questions/73418423/macports-opt-local-bin-
 python3-cant-find-libiconv-symbol-unless-run-under-she

 https://superuser.com/questions/394219/compiling-php-on-os-x-iconv-works-
 only-if-forced-to-64-bit

 https://superuser.com/questions/736210/how-do-i-remove-an-old-version-of-
 iconv-on-which-other-software-depends-and-ot

 https://trac.macports.org/ticket/43698

 https://trac.macports.org/ticket/50044

 https://trac.macports.org/ticket/57821

 https://www.cs.cmu.edu/~music/serpent/doc/installation-mac64.html

 https://www.mail-archive.com/haskell-cafe@haskell.org/msg69139.html

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