bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: regex-0.12's regex.h seems to have a little bug


From: Simon Josefsson
Subject: Re: regex-0.12's regex.h seems to have a little bug
Date: Fri, 07 Oct 2005 13:18:59 +0200
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

I forgot about this discussion for a while...

Stepan Kasal <address@hidden> writes:

> Hello,
>
> On Thu, Sep 22, 2005 at 12:36:46PM +0200, Simon Josefsson wrote:
>> Stepan Kasal <address@hidden> 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?

Yes.

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

See this thread:

http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/4281

The problem was that the proposed solution was contingent on the
release of many other packages.  I'm not even sure which CVS tag of
which projects I should be using in order to start working on applying
the fix to gnulib.

> 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.

This sound worse and worse to me.  Moving filenames and directory
structures from Makefile.am into configure.ac (possibly indirectly
through aclocal.m4) seems wrong.  But if somebody else will make this
work and will support it, then I'm all for it.

> 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...

Which CVS branch should I be using?  I recall some CVS tags in (I
think it was) automake was dropped, and hacking resumed on another
tag, or something.

Thanks,
Simon




reply via email to

[Prev in Thread] Current Thread [Next in Thread]