Changes between Initial Version and Version 1 of Ticket #47159, comment 4


Ignore:
Timestamp:
Mar 17, 2015, 11:32:24 AM (9 years ago)
Author:
dbevans (David B. Evans)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #47159, comment 4

    initial v1  
    1 Larry, this version of intltool has changes that break the builds of many ports that depend on it.  In particular, I suspect that all ports that currently autoreconf to update intltool.m4 to our patched version will break.  This includes many GNOME ports.   The change ([http://bazaar.launchpad.net/~intltool/intltool/trunk/revision/742 upstream bzr 742]) effects both intltool.m5 and po/Makefile.in.in which both need to match for things to work again.  In addition, in many cases, the change results in a change in the installed locale directory path.
     1Larry, this version of intltool has changes that break the builds of many ports that depend on it.  In particular, I suspect that all ports that currently autoreconf to update intltool.m4 to our patched version will break.  This includes many GNOME ports.   The change ([http://bazaar.launchpad.net/~intltool/intltool/trunk/revision/742 upstream bzr 742]) effects both intltool.m4 and po/Makefile.in.in which both need to be updated before running configure for things to work again.  In addition, in many cases, the change results in a change in the installed locale directory path.
    22
    33The fix is to do a full reconfiguration of each of the ports in question using intltoolize which generally is omitted when using autoreconf.  Typically this means using the upstream autogen.sh or similar to rebuild the configuration. I've confirmed that this works with several test cases.