After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 171328 - intltool tags in POTFILES.in are not supported with GNU gettext
intltool tags in POTFILES.in are not supported with GNU gettext
Status: RESOLVED INVALID
Product: intltool
Classification: Deprecated
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: intltool maintainers
intltool maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-23 09:58 UTC by Stepan Kasal
Modified: 2005-08-01 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stepan Kasal 2005-03-23 09:58:18 UTC 
With GNU gettext, configure creates po/Makefile from the just generated
po/Makefile.in and from po/POTFILES.in, in one step---the code is registered by
AC_CONFIG_COMMANDS.  That code creates po/POTFILES, replacing the one created by
the code registered by intltool.m4 using AC_CONFIG_CONMMANDS_PRE.

This means that if POTFILES.in contains intltool tags ([...], [encoding:...]),
thank these tags will get into the generated Makefile.  make then fails,
claiming that it doesn't know how to create file "../[encoding:...]".
Comment 1 Rodney Dawes 2005-06-10 19:59:14 UTC 

*** This bug has been marked as a duplicate of 171330 ***
Comment 2 Stepan Kasal 2005-07-21 10:59:49 UTC 
No, this bug differs from bug #171330.

This is a serious problem in interaction between recent versions of GNU gettext
and intltool.

The easiest fix is to stop claiming that intltool works with (recent versions
of) GNU gettext.
Comment 3 Rodney Dawes 2005-07-21 15:07:22 UTC 
Intltool does work with the most recent versions of GNU gettext. You are doing
something to actively break that, because the inverse is not true, and gettext
does not support a feature of intltool. If these tags get removed from
POTFILES.in by intltool, then this is not a problem. The patch in 171330 has
apparently been approved by danilo, and committed, therefore this should no
longer be a problem.

*** This bug has been marked as a duplicate of 171330 ***
Comment 4 Stepan Kasal 2005-08-01 10:17:16 UTC 
I admit that my original description of the bug was confusing.

I should have started by describing the symptoms, not the cause, especially when
the cause was so complicated.

I made a new attempt, as bug #312217.