× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Actually, in my experience, this is automake's fault, not autoconf.
If I have automake 1.6 with autoconf 2.53, I do not get these errors.
But, with automake 1.5, and the same autoconf, I do get the errors.

At any rate, they are just warnings, and do not appear to prevent things
from working....   Though, please tell me if it's different for you.

The updated macros are necessary in order to be compatible with RedHat 8.0,
the old macros wouldn't even compile on that system...   the problem is
that autoconf/automake/libtool (one of those, anyway) broke it's backward
compatibility.   I felt it was better to support the new versions and make
CVS users upgrade their software, rather than have it unbuildable on a
newer system.

Here's the original thread (from November) in the archives:
http://archive.midrange.com/linux5250/200211/msg00016.html

It should perhaps be noted that this does not affect "releases" of tn5250,
it only affects those building from CVS.


On Wed, 5 Feb 2003, James Rich wrote:
> when I run autogen.sh I get the following two errors:
>
> configure.in:23: warning: do not use m4_patsubst: use patsubst or
> m4_bpatsubst
> configure.in:235: warning: do not use m4_regexp: use regexp or m4_bregexp
>
> I suppose my version of autoconf may not be new enough (autoconf (GNU
> Autoconf) 2.53).
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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