Hello,

On Thu, Sep 22, 2005 at 12:36:46PM +0200, Simon Josefsson wrote:
> Stepan Kasal <[EMAIL PROTECTED]> writes:
> > Later on, when it was realized that a fix is needed, it was decided to wait
> > for Autoconf 2.60, instead of converting gnulib back to the old scheme and 
> > later again to the new one.
> 
> Right, sure.  Btw, can I test this now?  Is autoconf CVS HEAD
> sufficient?  Do I need other tools from CVS?

oops, we got too far.  I'm afraid I no longer know what I'm speaking about.
 :-(

What was the problem?  That you cannot use AC_LIBOBJ/AC_LIBSOURCE with more
than one "lib" subdirectory, right?

What was the proposed solution?  I'm not sure, I'm afraid I have missed it.

But I _think_ that a prerequisite of the solution was that AC_LIBSOURCES and
AC_LIBOBJ would take a second parameter which would specify the "group"
that the file belongs to.
This prerequisite is not in CVS Autoconf.

I'm afraid we need a design document for the solution.  Then we can implement
it.  Have I missed it, or it is yet to be written?

The following doesn't seem to be much relevant now, but:
> I recall some release dependency tree.

CVS Automake requires CVS Autoconf.

The other dependecies are not relevant here:
CVS m4 requires CVS libtool (a.k.a. libtool 2.0).
And perhaps CVS libtool depends on something, too...

Happy hacking ;-)

Stepan


_______________________________________________
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib

Reply via email to