Hello,
I propose the patch attached below; an explanation follows:
I think that when AC_LIBOBJ and friends was designed, the idea was
to use
some testing
if foo_is_broken; then
AC_LIBOBJ([foo])
fi
The AC_LISOURCE/AC_LIBSOURCES macros were also made
Hello,
On Fri, Sep 23, 2005 at 02:37:06PM +0200, Bruno Haible wrote:
Stepan Kasal wrote:
But in the basic case, when only the implementation is fixed and no
header is needed, I see no advantage in adding a redundant call to
AC_LIBSOURCES.
The advantage is simplicity and consistency.
I
