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

Re: [XaraXtreme-dev] configure.in:305: error: possibly undefined macro: AM_GNU_GETTEXT

Vasil Dimov wrote:
On Fri, Jun 02, 2006 at 03:28:10PM +0100, Alex Bligh wrote:

OK, I understand looking for ranlib, but why drop the libtool stuff?
(not that I can immediately think what it is used for).

Because I get error about it, look below.

Sure, but /why/ are you seeing the error when we aren't?

The problem is that I get error (or at least I got some time ago when I
initially ported XaraLX to FreeBSD) about PKG_CHECK_MODULES. The port
itself has assured that gtk is available by specifying

Yes of course, but we can't delete it from configure.in as it can be
built on multiple systems - ideally including the FreeBSD user who
simply downloads the tarball.

This looks for pango, and includes its CFLAGS which is needed
for rendering. Surely FreeBSD supports Pango?

Yes, FreeBSD supports Pango, the problem is (or was) that the
PKG_CHECK_MODULES emitted errors. The port itself has assured that
pango is installed and available on the system prior to doing
autoreconf, configure and make

See above. This is fine if the change merely a diff to make a
port compile, but can't go into svn in the general case. Equally,
it /should/ be possible to write configure.in in a manner which
works on all platforms.

Its defined by the port in the configure's environment the following
CPPFLAGS_APPEND="`pkg-config --cflags atk fontconfig gdk-2.0 pango` -I/usr/local/include/atk-1.0/atk -I/usr/X11R6/include/gtk-2.0/gtk"
(sorry, this is a little hackish I hope to get rid of it someday...)

Presumably by making PKG_CHECK_MODULES work (or at least finding out
what the problem is)?

At a guess, does that define AM_GETTEXT rather than AM_GNU_GETTEXT?

No, it defines AM_GNU_GETTEXT, I guess autoreconf is not including
autoreconf -I /usr/local/share/aclocal does not help either

But I still don't understand the necessity to delete all the pango
stuff. How can font rendering work without it?

It's just the PKG_CHECK_MODULES that was deleted, otherwise the pango is
available on the system at compile time and the build is picking it up
via the hacked CPPFLAGS_APPEND which contains the result from
`pkg-config --cflags pango`, see above.

It sounds like autoconf is fundamentally not working as expected on
your system. At least 3 macros are simply not being found. Rather than
deleting macros, we should be finding out why.