m4-patches
[Top][All Lists]
Advanced

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

Re: 13-m4-undivert-culprit.patch


From: Gary V. Vaughan
Subject: Re: 13-m4-undivert-culprit.patch
Date: Sun, 26 Aug 2001 15:07:31 +0100
User-agent: Mutt/1.2.5i

On Mon, Aug 20, 2001 at 08:50:50PM +0200, Akim Demaille wrote:
> | > Anyway, now that I see what it is used for, it is clear to me that
> | > pseudo `echo' is something that M4sh must provide (and as a matter of
> | > fact I had removed NOTICE precisely to introduce M4SH-INIT, a very
> | > early diversion used by M4sh to output its initialization stuff before
> | > Autoconf's).  So that diversion name will no longer be needed.  And I
> | > guess there are many other sh idioms to move from Libtool to M4sh.
> | 
> | Okay.  I think that libtool's requirement for a non-backslash
> | intepreting echo is quite unusual -- are you planning to migrate that
> | functionality from libtool.m4 into m4sh.m4?
> 
> Yes, I do.  It is not unusual and actual Autoconf is in bad need for
> such a feature.  For instance we know that our smally heredocs for
> AC_DEFINE and so on are extremely costly.  But we can't take any
> risks, hence heredocs.  With a good echo, we're done, and then it
> speeeeeeeeeeeeeds again.

Cool.  There is a lot of funny interaction between libtool.m4 and
ltmain.sh that makes this work IIRC -- I'll be happy to help out with
any awkwardness you encounter when you move that code over.

> There were impressive figures about GCC's configure slowness on some
> arch precisely because of these heredocs.

Is GCC using autoconf now?  Wow, shows how much attention I've been
paying.  I thought the whole tree ran from Cygnus configure.

Cheers,
        Gary.
-- 
  ())_. Gary V. Vaughan     gary@(oranda.demon.co.uk|gnu.org)
  ( '/  Research Scientist  http://www.oranda.demon.co.uk       ,_())____
  / )=  GNU Hacker          http://www.gnu.org/software/libtool  \'      `&
`(_~)_  Tech' Author        http://sources.redhat.com/autobook   =`---d__/



reply via email to

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