[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in gettextize or related components
From: |
Bruno Haible |
Subject: |
Re: Bug in gettextize or related components |
Date: |
Tue, 16 Mar 2004 19:45:38 +0100 |
User-agent: |
KMail/1.5 |
Hi,
> I'm running into a bit of a problem with anjuta which looks as if it has
> its genesis in gettextize. I can't trace down the precise source of the
> problem code, but perhaps someone more familiar with the (very complex!)
> structure of the m4/automake/autoconf files and structures can do so.
> Here's the bottom line.
>
> In a project autogenerated with anjuta, the directory <project root>/po
> contains the following in Makefile.in.in, installed by gettextize:
> ...
> MKINSTALLDIRS = @MKINSTALLDIRS@
> mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo
> "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
>
> After running ./configure, Makefile.in contains the following:
> ...
> MKINSTALLDIRS = $(top_builddir)/./mkinstalldirs
> mkinstalldirs = $(SHELL) `case "$(MKINSTALLDIRS)" in /*) echo
> "$(MKINSTALLDIRS)" ;; *) echo "$(top_builddir)/$(MKINSTALLDIRS)" ;; esac`
It looks like you are using a Makefile.in.in from GNU gettext 0.11.5 or
older with a gettext.m4 + nls.m4 from GNU gettext 0.12 or newer. This
cannot work.
If all went well after running gettextize, the po/Makefile.in.in and
the m4/gettext.m4 should come from the same GNU gettext version (do
"gettextize --version" to see which one).
Another possible cause is that m4/gettext.m4 is up to date but is not
taken into account because 'aclocal' is run without the options that
make it look in the m4/ directory.
> All copies of Makefile.in.in which I could find
> explicitly declared 'mkinstalldirs = $(MKINSTALLDIRS)'
These are the Makefile.in.in from GNU gettext >= 0.12.
Another possible cause is that configure.in is not using AM_GNU_GETTEXT
at all but some other version (e.g. AM_GLIB_GNU_GETTEXT) under the
responsibility of the GNOME people.
Can you show the relevant parts of configure.in?
Bruno