autoconf-patches
[Top][All Lists]
Advanced

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

Re: autoreconf gets autopoint order wrong?


From: Akim Demaille
Subject: Re: autoreconf gets autopoint order wrong?
Date: 08 Oct 2002 10:23:46 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)

| %% Akim Demaille <address@hidden> writes:
|   ad> aclocal is to be run twice: one first time to make sure all the
|   ad> macros that might be used are imported, so that, for instance, if
|   ad> you use PDS_USUAL_STUFF which includes an invocation of
|   ad> AM_GNU_GETTEXT, or AC_PROG_LIBTOOL etc. be found.
| 
| But that doesn't help if the _first_ aclocal fails and exits (causing
| autoreconf to quit) before it runs autopoint (which is what happens).

Oops, sorry, I completely missed that point.


|   | So, for now autoreconf is not helpful to me.  I wonder if the order in
|   | which these things are done could be changed so autopoint is done first
|   | rather than second?
| 
|   ad> The problem is that we are using recipees that different from tool
|   ad> to tool.  Since autopoint still just greps configure.ac to see if
|   ad> AM_GNU_GETTEXT_VERSION is used, autoreconf can do the same.  So I
|   ad> would suggest having autoreconf to grep AM_GNU_GETTEXT_VERSION
|   ad> configure.ac after the first aclocal run.
| 
| I don't see how this will help; maybe I'm misunderstanding your
| suggestion.
| 
| The first aclocal fails due to missing macros, and so autoreconf fails.
| Are you saying autoreconf should look at why aclocal failed, and not
| exit itself if the error was due to AM_GNU_GETTEXT* macros?
| 
| While that would work, I guess, there would still be errors printed,
| which would be disconcerting.
| 
| I don't understand why you don't want to simply run autopoint before the
| first aclocal--is there some reason that this won't work or is a bad
| idea?

Well, it's because when we were relying on gettextize, and not
autopoint, calling it before knowing whether you wanted it or not
simply resulted in importing Gettext everywhere.

I am still not confortable with systematically autopoint, as you seem
to suggest.  I'd like to point out that a typical installation of
gettext makes the most recent m4 files visible to aclocal: that's why
this problem was never reported before.

Could you try this autoreconf please?  If it works, could someone
install it?  I can't: my organisation still has no Internet connection
that allows me to run CVS :(


2002-10-08  Akim Demaille  <address@hidden>

        * bin/autoreconf.in (&autoreconf): Run autopoint before the first
        aclocal invocation, as Gettext macros might not be visible to
        aclocal.
        Instead of blindly running autopoint, scan configure.ac (not the
        traces) for AM_GNU_GETTEXT_VERSION uses, as autopoint does.
        Reported by Paul D. Smith.

I wish I could send a diff, but I just realized XEmacs didn't keep the
usual autoreconf.in~ :(

Attachment: autoreconf.in
Description: Text document


reply via email to

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