Failed to configure texinfo

[tim@…]

log files attached Full screen dump of port upgrade follows:

sudo port upgrade outdated
--->  Fetching archive for ncurses
--->  Attempting to fetch ncurses-6.0_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/ncurses
--->  Attempting to fetch ncurses-6.0_0.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ncurses
      [                                        ]   0.0 %        speed: 0 B/s        --->  Attempting to fetch ncurses-6.0_0.darwin_11.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/ncurses
--->  Fetching distfiles for ncurses
--->  Attempting to fetch ncurses-6.0.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/ncurses
--->  Verifying checksums for ncurses
--->  Extracting ncurses
--->  Applying patches to ncurses
--->  Configuring ncurses
--->  Building ncurses
--->  Staging ncurses into destroot
--->  Installing ncurses @6.0_0
--->  Cleaning ncurses
--->  Deactivating ncurses @5.9_2
--->  Cleaning ncurses
--->  Activating ncurses @6.0_0
--->  Cleaning ncurses
--->  Computing dependencies for gettext
--->  Fetching archive for gettext
--->  Attempting to fetch gettext-0.19.5_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/gettext
--->  Attempting to fetch gettext-0.19.5_1.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/gettext
--->  Attempting to fetch gettext-0.19.5_1.darwin_11.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/gettext
--->  Fetching distfiles for gettext
--->  Attempting to fetch gettext-0.19.5.tar.gz from http://sea.us.distfiles.macports.org/macports/distfiles/gettext
--->  Verifying checksums for gettext
--->  Extracting gettext
--->  Configuring gettext
--->  Building gettext
--->  Staging gettext into destroot
--->  Installing gettext @0.19.5_1
--->  Cleaning gettext
--->  Computing dependencies for gettext
--->  Deactivating gettext @0.19.5_0
--->  Cleaning gettext
--->  Activating gettext @0.19.5_1
--->  Cleaning gettext
--->  Computing dependencies for texinfo
--->  Fetching archive for texinfo
--->  Attempting to fetch texinfo-6.0_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/texinfo
--->  Attempting to fetch texinfo-6.0_1.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/texinfo
--->  Attempting to fetch texinfo-6.0_1.darwin_11.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/texinfo
--->  Fetching distfiles for texinfo
--->  Attempting to fetch texinfo-6.0.tar.xz from http://sea.us.distfiles.macports.org/macports/distfiles/texinfo
--->  Verifying checksums for texinfo
--->  Extracting texinfo
--->  Configuring texinfo
Error: Failed to configure texinfo, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texinfo/texinfo/work/texinfo-6.0/config.log
Error: org.macports.configure for port texinfo returned: configure failure: command execution failed
Please see the log file for port texinfo for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_texinfo/texinfo/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

[ryandesign (Ryan Carsten Schmidt)]

Ok, the main.log says:

:info:configure dyld: Library not loaded: /opt/local/lib/libncurses.5.dylib
:info:configure   Referenced from: /opt/local/lib/libreadline.6.dylib

ncurses has already been upgraded to version 6, but your readline is still using ncurses 5. You can fix the problem by upgrading readline first, then upgrading texinfo.

texinfo itself doesn't require readline. But texinfo does require awk for this part of the configuration. The texinfo port doesn't declare a dependency on awk, because little text-processing utilities like awk, sed and grep are already installed as a part of OS X, and those versions are usually good enough. However, you already have the gawk port installed, so texinfo used that, but gawk uses readline.

[udbraumann]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Were you able to resolve this problem by either first upgrading or deactivating the gawk port?

[ryandesign (Ryan Carsten Schmidt)]

Or by using trace mode (i.e. the -t flag) when upgrading texinfo?

[udbraumann]

For me upgrading readline first resolved the problem. Own software previously relying on libncurses.5.dylib was requiring rebuilds.

[ryandesign (Ryan Carsten Schmidt)]

Replying to braumann@…:

For me upgrading readline first resolved the problem.

Ok good. Unfortunately I'm not sure we have a way of preventing this problem in MacPorts, since texinfo doesn't actually declare a dependency on gawk and we don't particularly want to add one because the awk in OS X should be sufficient. The problem is that autoconf, which is used by texinfo and which I estimate is the most popular configuration system among those used by ports, checks first if gawk exists, and only if it does not does it fall back to using awk, hence a "broken" gawk will interfere with many many ports' builds. The only possible solution I can think of is enabling trace mode by default, which is something we've been considering. Cc'ing Josh in case he can think of another way...

Own software previously relying on libncurses.5.dylib was requiring rebuilds.

Certainly.

[jmroot (Joshua Root)]

Replying to ryandesign@…:

The problem is that autoconf, which is used by texinfo and which I estimate is the most popular configuration system among those used by ports, checks first if gawk exists, and only if it does not does it fall back to using awk, hence a "broken" gawk will interfere with many many ports' builds. The only possible solution I can think of is enabling trace mode by default, which is something we've been considering. Cc'ing Josh in case he can think of another way...

Yeah, not really, short of patching autoconf and autoreconfing everything.

[tim@…]

I'm the OP. The solution as described here works for me. Good work!

[ryandesign (Ryan Carsten Schmidt)]

Great. Then I'll mark the ticket as resolved, though we're not fixing anything about this in MacPorts right now. Hopefully we can enable trace mode by default in the future (once any remaining bugs in trace mode have been fixed) which will solve this kind of problem.