Re: snapshot in preparation for m4-1.4.11.51-5116

2008-09-29 Thread Elbert Pol
Hoi, Bruno Haible wrote: Elbert Pol wrote: $ gdb test-open.exe break rpl_open run break 116 continue nexti print statbuf nexti print statbuf nexti print statbuf nexti print statbuf nexti print statbuf nexti print statbuf ne

Re: snapshot in preparation for m4-1.4.11.51-5116

2008-09-28 Thread Bruno Haible
Elbert Pol wrote: > >$ gdb test-open.exe > >break rpl_open > >run > >break 116 > >continue > >nexti > >print statbuf > >nexti > >print statbuf > >nexti > >print statbuf > >nexti > >print statbuf > >nexti > >print statbuf > >nexti > >

Re: snapshot in preparation for m4-1.4.11.51-5116

2008-09-28 Thread Elbert Pol
Hello, Bruno Haible wrote: Elbert Pol wrote: I attach the logs This is with os/2 Except for the well-known SIGFPEs (which are most probably caused by computations with NaNs) there are new failures of test-open and test-fopen. config.log has configure:18187: checking whether fopen re

Re: snapshot in preparation for m4-1.4.11.51-5116

2008-09-27 Thread Bruno Haible
Elbert Pol wrote: > I attach the logs > > This is with os/2 Except for the well-known SIGFPEs (which are most probably caused by computations with NaNs) there are new failures of test-open and test-fopen. config.log has configure:18187: checking whether fopen recognizes a trailing slash c

Re: snapshot in preparation for m4-1.4.11.51-5116

2008-09-27 Thread Elbert Pol
Hello Eric, I have use now gcc 3.4.6 instead of the 3.3.5 I run the M4 and the ./configure and make runs fine. But with the make -k check there are some errors. I attach the logs This is with os/2 Thankz for all :) check.out.lzma Description: Binary data config.log.lzma Descript