[MacPorts] #67317: gettext @0.21.1: tries to use msgfmt, gmsgfmt, xgettext, msgmerge, which might be broken by gettext-tools-libs update (was: gettext @0.21 builds incorrectly on PPC Leopard, Mac OS X 10.5.8)

[MacPorts]

#67317: gettext @0.21.1: tries to use msgfmt, gmsgfmt, xgettext, msgmerge, which
might be broken by gettext-tools-libs update
------------------------+------------------------
  Reporter:  ballapete  |      Owner:  ryandesign
      Type:  defect     |     Status:  accepted
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.8.1
Resolution:             |   Keywords:
      Port:  gettext    |
------------------------+------------------------
Changes (by ryandesign):

 * status:  new => accepted
 * owner:  (none) => ryandesign
 * keywords:  leopard ppc =>
 * cc: ryandesign@… (removed)


Comment:

 Replying to [ticket:67317 ballapete]:
 > When building these errors appear that signify that before parts of
 `gettext` (`gettext-tools-libs` or `libtextstyle`) were incorrectly
 upgraded because they left the application programmes unusable:
 >
 > {{{
 > Dyld Error Message:
 >   Library not loaded: /opt/local/lib/libgettextsrc-0.21.dylib
 >   Referenced from: /opt/local/bin/msgfmt
 >   Reason: image not found
 > }}}

 The libtextstyle port provides the libtextstyle.0.dylib library, which
 hasn't changed since it was introduced, so there's no problem there.

 gettext-tools-libs was not incorrectly upgraded; it was upgraded in the
 only way that it can be. gettext-tools-libs 0.21 provided
 libgettextlib-0.21.dylib and libgettextsrc-0.21.dylib. These files were
 removed when the port was upgraded to 0.21.1. It now provides
 libgettextlib-0.21.1.dylib and libgettextsrc-0.21.1.dylib. This leaves any
 gettext programs that use those libraries—like msgfmt, gmsgfmt, xgettext,
 and msgmerge—broken until the gettext port is upgraded. These are internal
 libraries, by the way, intended for use by gettext and nobody else, so
 only the gettext port's programs should be broken as a result of this. The
 bug, therefore, seems to be that the build of gettext is itself attempting
 to use (or at least checking for the existence of) the msgfmt, gmsgfmt,
 xgettext, and msgmerge programs installed by its former version, and the
 fix is probably to prevent it from doing that:

 > {{{
 > --->  Configuring gettext
 > ...
 > checking for msgfmt... ./configure: line 23487: 77484 Trace/BPT trap
 $ac_dir/$ac_word --statistics /dev/null 1>&5 2>&1
 > no
 > checking for gmsgfmt... :
 > checking for xgettext... ./configure: line 23610: 77494 Trace/BPT trap
 $ac_dir/$ac_word --omit-header --copyright-holder= --msgid-bugs-address=
 /dev/null 1>&5 2>&1
 > no
 > checking for msgmerge... ./configure: line 23688: 77503 Trace/BPT trap
 $ac_dir/$ac_word --update -q /dev/null /dev/null 1>&5 2>&1
 > no
 > }}}

 Does this issue prevent the gettext port from building or is it just that
 you noticed these messages in the log?

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