>>>>> "Bernard" == Bernard Dautrevaux <[EMAIL PROTECTED]> writes:

Bernard> There is one test that fails, the autoupdate test (test 111
Bernard> in my case).  

This is a known problem of autoupdate: it needs a powerful sed.  I'm
thinking about rewriting it in Perl.  Contribution are highly
appreciated :)

I'll change autoupdate so that it checks sed is GNU sed, this is
catching way too many people.  I apologize for not having done this before.

Bernard> There is two problems in this test:

Bernard> First when creating "au.txt" using "autoconf --trace"
Bernard> autoconf was not able to find "acversion.m4"; I must say that
Bernard> I build autoconf in a subdirectory (name autoconf-native) of
Bernard> the autoconf directory; what seems to happen is that
Bernard> autoupdate is started with an autoconf_dir set to ../.., that
Bernard> is the source directory; however "acversion.m4" is in the
Bernard> build directory :-)

This is bizarre: make distcheck works fine and it runs a very similar
layout.  I just checked what you said:

        tar zxvf autoconf
        cd autoconf
        mkdir build
        cd build
        ../configure
        make check

and it works fine.  It must be related to the other problem.


Bernard> I know I could install gnu sed, but not everybody is allways
Bernard> willing to. 

I agree, nevertheless I will not try to have autoupdate be portable.
Portability is a PITA, and I won't devote time for portability issues
on the maintainer side.



Bernard> OTOH, there is only two sed scripts generated from au.txt,
Bernard> and only one use of each, so splitting them in less than 50
Bernard> line scripts (as is done for the scripts generated by
Bernard> config.status) should not be too complicated.

Bernard> Any better ideas?

Rewrite everything in Python :)

Reply via email to