I'm seeing these tests failing:
70 72 73 74 75 76 77 78 79 80 81 82 83 84 85 90
I committed my patches anyway after making sure they were preexisting,
but someone should look at them... be careful, please.
Paolo
___
Autoconf mailing list
Autoconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paolo Bonzini on 10/6/2007 4:14 AM:
> I'm seeing these tests failing:
>
> 70 72 73 74 75 76 77 78 79 80 81 82 83 84 85 90
>
> I committed my patches anyway after making sure they were preexisting,
> but someone should look at them... be
I'm not seeing it here. Perhaps you have a bad merge?
Since the last commit is mine, you would have got it too. :-)
resolve it, could you post a failing testsuite.log (either of the whole
run, or from your choice of one of the tests/testsuite.dir/??? failures)
for inspection?
Might be an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paolo Bonzini on 10/6/2007 7:49 AM:
> Might be an m4 problem? Let's start with the md5sum of testsuite:
>
> 41edcfeffee5f2c2f913f8f780d1dda1 testsuite
Same sum here,
>
> My m4 is
>
> GNU M4 1.4.8
... but with M4 1.4.10. So I think
... but with M4 1.4.10. So I think we can rule out an m4 bug for
generating the testsuite correctly. Perhaps you are tripping over a shell
bug? I tested with bash 3.2.25.
Indeed mine is 2.05b.
Paolo
___
Autoconf mailing list
Autoconf@gnu.org
ht
Hello Paolo,
* Paolo Bonzini wrote on Sun, Oct 07, 2007 at 03:16:44PM CEST:
>
>> ... but with M4 1.4.10. So I think we can rule out an m4 bug for
>> generating the testsuite correctly. Perhaps you are tripping over a shell
>> bug? I tested with bash 3.2.25.
>
> Indeed mine is 2.05b.
FWIW I can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paolo Bonzini on 10/7/2007 7:16 AM:
>
>> ... but with M4 1.4.10. So I think we can rule out an m4 bug for
>> generating the testsuite correctly. Perhaps you are tripping over a
>> shell
>> bug? I tested with bash 3.2.25.
>
> Indeed mi
