I knew this was going to happen. :)

The problem was that it didn't work with newer automake/autoconf...  so I
fixed that, and now it doesn't work with older automake/autoconf.
But, I guess this is the better direction to err in.

On some boxes I'm using Automake 1.5, and Autoconf 2.53 and it works fine.
Autoconf will complain about some of the M4 code generated by Automake,
but it still works.

On other boxes I have a newer version of Automake... I think 1.61, but
I can't currently get to those boxes to check...  but on those machines
I get no errors at all.  Same version of Autoconf.

The version of Libtool that you're using should be fine.

On my RedHat 7.1 box I upgraded by grabbing the source for automake &
autoconf from http://www.gnu.org doing:

    rpm -e automake
    rpm -e autoconf
    rpm -e glib-devel
    tar xvzf automake.tar.gz
    cd automake
    ./configure --prefix=/usr
    make
    make install
    tar xvzf autoconf.tar.gz
    cd autoconf
    ./configure --prefix=/usr
    make
    make install
    mount /mnt/cdrom
    cd /mnt/cdrom/RedHat/RPMS
    rpm -i glib-devel.whatevertherestofthefilenameis.rpm



On Wed, 20 Nov 2002, Brian Finn wrote:

> Hi all,
>
> What versions of Automake, Autoconf, and libtool should I have to
> compile TN5250? I have an old Red Hat 6.1 box on my desktop, and I
> thought I would try and compile the CVS version for grins. ./autogen.sh
> reported:
>
> 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])
>
> I appear to have:
> Automake version 1.4
> Autoconf version 2.13
> libtool version 1.4.2
>
> It's not a big deal. I'm just curious. :)
>
> Thanks,
> Brian Finn



This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2020 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].