[MacPorts] ProblemHotlist modified

[MacPorts Wiki]

Page "ProblemHotlist" was changed by raimue
Diff URL: <https://trac.macports.org/wiki/ProblemHotlist?action=diff&version=140>
Revision 140
Comment: Restore deleted items in Retired section
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ProblemHotlist
=========================================================================
--- ProblemHotlist (version: 139)
+++ ProblemHotlist (version: 140)
@@ -148,6 +148,52 @@
 The following problems are now solved, no longer apply to current MacPorts or should no longer be happening due to other circumstances. They are kept here for future reference and to avoid breaking existing links.
 }}}
 
+== Build failures after upgrading to ncurses 6 == #ncurses6
+
+After upgrading ncurses to version 6, a port may fail to build, with the following error message in the main.log or config.log file:
+
+{{{
+dyld: Library not loaded: /opt/local/lib/libncurses.5.dylib
+  Referenced from: /opt/local/lib/libreadline.6.dylib
+  Reason: no suitable image found.  Did find:
+	/usr/lib/libncurses.5.dylib: no matching architecture in universal wrapper
+}}}
+
+The solution is to upgrade readline:
+
+{{{
+sudo port upgrade readline
+}}}
+
+Then clean the port that originally failed to build, and try to build it again.
+
+The problem occurs when building ports that use an autotools-based configure script, after having upgraded ncurses to version 6 but before having upgraded readline to use ncurses 6. The reason the problem occurs is that part of the boilerplate that autotools bakes into every configure script is to locate an awk implementation. The first one it checks for is gawk, so if the gawk port happens to be installed, a configure script will try to use that. gawk depends on readline, which depends on ncurses, and if you have upgraded ncurses but haven't upgraded readline to use the new ncurses, then gawk will be broken.
+
+MacPorts usually upgrades dependencies first, so you wouldn't see this problem if gawk were listed as a dependency of the port that failed to build. But we don't want to add unnecessary gawk dependencies to thousands of configure-based ports when the awk implementation that's part of OS X would work just as well.
+
+
+== Port installation fails with "no destroot found" == #nodestrootfound
+
+Installing a port fails with the error message "no destroot found", for example:
+
+{{{
+:error:install org.macports.install for port libpixman returned: no destroot found at: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpixman/libpixman/work/destroot
+}}}
+
+We do not know what causes this occasional problem, but the solution is to clean the affected port and try again. For example the above error shows libpixman is the port that failed, so to clean it you would run:
+
+{{{
+sudo port clean libpixman
+}}}
+
+
+
+== Error message from "port upgrade outdated": uninstall failure: "an invalid entry was passed" == #interrupteduninstall
+
+Before MacPorts 2.1.3 it was possible to leave the registry in an inconsistent state if an uninstallation was interrupted. Although this has been fixed in version 2.1.3, the fix does not cure a previously corrupt registry.
+
+The perl script attached to the ticket [ticket:34482 about this bug] fixes the registry. The direct link is [attachment:ticket:34482:macports_34482_fix here].
+
 
 == MacPorts `port install`s fail after an OS X upgrade ==
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/ProblemHotlist>
MacPorts <https://www.macports.org/>
Ports system for macOS

This is an automated message. Someone added your email address to be
notified of changes on 'ProblemHotlist' page.
If it was not you, please report to admin at macports.org.