bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug with top_builddir in Makefile.in.in in gettext 0.11.2


From: Martin Norbäck
Subject: Re: bug with top_builddir in Makefile.in.in in gettext 0.11.2
Date: 17 Jun 2002 14:26:27 +0200

mån 2002-06-17 klockan 13.56 skrev Bruno Haible:
> Martin Norbäck wrote:
> > Makefile.in.in does not define top_builddir anymore, this means that the
> > following dependency fails:
> > 
> > Makefile: Makefile.in.in $(top_builddir)/config.status POTFILES.in
> > 
> > This was changed from the previous version. It seems these variables has
> > moved to a file called Makevars.template, not Makevars. Seems like you
> > have to copy the file by hand.
> 
> It was moved to a file called Makevars, and the package maintainer is
> expected to create this file.
> 
> > This is not good, because things like rpm runs gettextize automatically,
> 
> It shouldn't do so. gettextize is an interactive tool.
> 
> > and if the package is not already built with gettext 0.11.2 (very few
> > packages are), then it will fail.
> 
> The failure is expected. Upgrading from one gettext version to another
> requires maintainer attention, in particular reading the gettext
> documentation and the gettextize output.
> 
> > cp po/Makevars.template po/Makevars
> > 
> > to the build rules.
> 
> It is wrong, because it will kill settings that the maintainer has
> already made in po/Makevars.

Thanks for the clarification! By closer examination it seems that
gettextize is only invoked when using %GNUconfigure, not with
%configure.

The %configure macro still does to much, like invoke libtoolize, I will
take this up with the rpm people.

Regards,

        Martin


Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]