Re: AC_LIBOBJ vs LIBOBJS w/ backward-compatibility?

[Pekka Savola]

On Mon, 7 Apr 2003, Andreas Schwab wrote:
> |> I've a configure.in file which uses LIBOBJS which I can port to use
> |> AC_LIBOBJ just fine.
> |> 
> |> However, there is no form which could be made to work on both autoconf
> |> 2.13 and autoconf >= 2.53: AC_LIBOBJ is not supported in the 
> |> former, and LIBOBJS fails in the latter.
> |> 
> |> Is there a way to move to AC_LIBOBJ in a backward-compatible manner?
> |> For example, is there a nice conditional macro definition for AC_LIBOBJ   
> |> that could be applied as necessary (I don't think so), or some other
> |> mechanism?
> 
> How about using ifdef([AC_LIBOBJ],,AC_DEFUN([AC_LIBOBJ], ...))?

Unfortunately the code for AC_LIBOBJ is too complicated for this, but one
can work around the problems by using m4_pattern_allow() until no
backward-compatibility is necessary.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings