| 43 | | |
| 44 | | == Build failures after upgrading to ncurses 6 == #ncurses6 |
| 45 | | |
| 46 | | 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: |
| 47 | | |
| 48 | | {{{ |
| 49 | | dyld: Library not loaded: /opt/local/lib/libncurses.5.dylib |
| 50 | | Referenced from: /opt/local/lib/libreadline.6.dylib |
| 51 | | Reason: no suitable image found. Did find: |
| 52 | | /usr/lib/libncurses.5.dylib: no matching architecture in universal wrapper |
| 53 | | }}} |
| 54 | | |
| 55 | | The solution is to upgrade readline: |
| 56 | | |
| 57 | | {{{ |
| 58 | | sudo port upgrade readline |
| 59 | | }}} |
| 60 | | |
| 61 | | Then clean the port that originally failed to build, and try to build it again. |
| 62 | | |
| 63 | | 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. |
| 64 | | |
| 65 | | 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. |
| 66 | | |
| 67 | | |
