This worked for me for automake, autoconf, and libtool:

automake --version
autoconf --version
libtool --version

I'm not sure about glib though. YMMV :)

Brian Finn

On Wed, 5 Mar 2003, Jerome Draper wrote:

> How do I tell what versions I have installed of what you have shown below?
> 
> J
> 
> ----- Original Message -----
> From: Brendan Bispham <b.bispham@xxxxxxxxxxxxxxxxxx>
> To: <LINUX5250@xxxxxxxxxxxx>
> Sent: Wednesday, March 05, 2003 9:30 AM
> Subject: [LINUX5250] Trouble with autogen.sh
> 
> 
> > Hi,
> >
> > Trying the CVS source, and ran into problems with autogen. However I think
> I'm
> > up to date;
> >
> > glib:2.2.1
> > automake: 1.6.3
> > autoconf:2.54
> > libtool:1.4.1-r9
> > glib-config --version reports 1.2.10
> >
> > I've checked and think I'm using the right versions - there seems to be a
> > script which selects which version automake/autoconf to call depending
> upon
> > such factors as AC_PREREQ (which is not there) or environment variables,
> but
> > I dont really know why it's so complex... Anyway, this is what I get:
> >
> > ./autogen.sh
> > autoconf: Undefined macros:
> > configure.in:234:AC_CONFIG_FILES([Makefile src/Makefile tn5250.spec
> > doc/Makefile linux/Makefile freebsd/Makefile win32/Makefile sun/Makefile
> > tn5250-config xt5250])
> > configure.in:3:AC_CONFIG_SRCDIR([src/tn5250.c])
> > autoconf: Undefined macros:
> > configure.in:234:AC_CONFIG_FILES([Makefile src/Makefile tn5250.spec
> > doc/Makefile linux/Makefile freebsd/Makefile win32/Makefile sun/Makefile
> > tn5250-config xt5250])
> > configure.in:3:AC_CONFIG_SRCDIR([src/tn5250.c])
> >
> > Can't think of anything else to try out...
> >
> > Ta,
> >
> >


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.