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 116308 - Support ./configure XGETTEXT=blah
Support ./configure XGETTEXT=blah
Status: RESOLVED WONTFIX
Product: glib
Classification: Platform
Component: build
2.2.x
Other Solaris
: Normal trivial
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2003-06-30 00:06 UTC by Michael C. Vergallen
Modified: 2013-02-03 06:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael C. Vergallen 2003-06-30 00:06:16 UTC
On Solaris there is allready a version of xgettext installed but when
installing GNU gettext with the --program-prefix=g it works. However you
should also check for the existance of gxgettext becuase otherwise what is
the use of having GNU gettext installed ?

On the same note it seems that searching for automake-1.4 only seams
restrictive. should one not search for versions equal or above a particular
release ?

It seems odd to me that when one has a version of libtool installed on the
system that one uses the libtool suplied with the librarie.
Comment 1 Owen Taylor 2003-08-07 16:38:07 UTC
I don't think searching for gxgettext makes sense (what
if you used --program-prefix=z?) , but being
able to override the paths to the gettext tools in the
standard autoconf way of setting environment variables
probably makes sense.

For the other two points:

 - automake versions are not compatible with each other,
   and automake supports parallel installation of multiple
   versions for this reason. GTK+-2.4.x will build with
   automake-1.7 and only automake-1.7.

   (Also, the automake version doesn't matter if you
   are using the tarballs)

 - Using libtool shipped with the package is the standard
   way of using libtool and the only way that is guaranteed
   to work. If you try to use the system 'libtool' binary,
   it may be incompatible with the configure script 
   shipped with the package.