bug-m4
[Top][All Lists]
Advanced

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

Re: m4-1.4.10 breaking autoconf?


From: Eric Blake
Subject: Re: m4-1.4.10 breaking autoconf?
Date: Sat, 21 Jul 2007 10:23:44 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070716 Thunderbird/2.0.0.5 Mnenhy/0.7.5.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Thomas Klausner on 7/21/2007 12:14 AM:
> On Fri, Jul 20, 2007 at 09:38:00PM -0600, Eric Blake wrote:
>> Thanks for the report.  I have re-bootstrapped m4 1.4.10 with itself, and
>> didn't have any problems on my cygwin platform with the resulting
>> configure script, so either the m4 configure.ac is simpler than mng's, or
>> m4 1.4.10 is tickling a platform-specific bug.  Hopefully you can help us
>> narrow in on the problem.
> 
> I can reproduce this problem with m4's configure script.
> The file created by running 'autoconf' is just 35354 bytes long, while
> the one distributed with the m4-1.4.10 tarball is 647263.
> I'll attach the generated configure file (m4-configure.bz2).

Thanks.  I need at least one more piece of information - could you send
the config.log created when you built m4-1.4.10 from the tarball?

> The testsuite works fine, but skips a few tests:
> 
> Skipped checks were:
>   ./094.changeword ./095.changeword ./096.changeword ./097.changeword
>   ./098.changeword ./099.changeword

The skips are to be expected, since you did not configure with
- --enable-changeword.  But that means the testsuite is not detecting your
bug, so once we figure out a root cause, I'll have to improve that.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGojLa84KuGfSFAYARAjXWAKDV+FysW/U0tUpxn0ZTdvP1kvcGPgCgvhJH
12VeeemSKztJ+BpAEZgjCcQ=
=33Ov
-----END PGP SIGNATURE-----




reply via email to

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