Eric Blake wrote on 2008-09-29:
> > On Irix 5.3 it skips test-cstack2.sh because it wants libsigsegv for full
> > c-stack functionality and I did not test with that
> > (Irix really needs libsigsegv 2.7 which is not yet released).
>
> That's Bruno's call
It's OK that the test-c-stack2.sh test is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom G. Christensen on 9/29/2008 1:00 PM:
>> Can you post the relevent section of config.log related to signbit tests?
>>
> I wasn't sure what parts would be considered relevant so I've dumped
> full config.log files and buildlogs at:
> ht
On Mon, Sep 29, 2008 at 06:05:07AM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 9/28/2008 4:16 AM:
> >
> > On Irix 6.x gnulib test-signbit still fails:
> > test-signbit.c:149: assertion failed
> > /bin/ksh[10]: 18432 Abort(coredump)
> > FAIL: test-signbit
>
> That line is "ASSERT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom G. Christensen on 9/28/2008 4:16 AM:
> I gave this a run on Irix 5.3, 6.2 & 6.5 using SGI compilers.
> Things look good and the m4 testsuite passes on all 3 platforms.
Good to hear!
> On Irix 5.3 it skips test-cstack2.sh because it w
On Fri, Sep 12, 2008 at 06:53:49AM -0600, Eric Blake wrote:
> I'm committing this. It looks like your flavor of NetBSD now handles
> denormals, but still fails on negative zero.
I asked around a bit -- this was a regression. NetBSD has two versions
of this code around, and recently switched back
Eric Blake wrote:
> > In the
> > 'double' case on mingw, in 'e' format, we need to use 3 digits for the
> > exponent, to match what MSVCRT does. This is not needed for 'long double' -
> > since 'long double' output is not supported by MSVCRT in the first place.)
>
> Actually, in the latest version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/18/2008 4:34 AM:
> (You apparently copied the code for 'double'.
Yes.
> In the
> 'double' case on mingw, in 'e' format, we need to use 3 digits for the
> exponent, to match what MSVCRT does. This is not needed for 'long
Eric Blake wrote:
> with both pieces in place, I've tested that Irix 5.3
> passes the testsuite. So here's what I'm pushing:
>
> From: Eric Blake <[EMAIL PROTECTED]>
> Date: Tue, 16 Sep 2008 09:36:24 -0600
> Subject: [PATCH] vasnprintf: support Irix 5.3
>
> * lib/vasnprintf.c (VASNPRINTF): Also
Bruno Haible clisp.org> writes:
> > > the system sprintf does not know how to print -0, so the result is
> > > 0.00 and lacks -. Does it make more sense to adjust the existing
> > > gl_PRINTF_INFINITE_LONG_DOUBLE (which also tests for NaN) to add a test
> > > for negative zero, or to add a n
Eric Blake wrote:
> Tom has (graciously) allowed me access to his Irix 5.3 system to attempt
> to address this.
Thanks for debugging this!
> > The test ends up calling sprintf(tmp, "%Ld", -0.0L), but
>
> excuse the typo; I meant "%Lf", not "%Ld"
>
> > the system sprintf does not know how to pri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 9/13/2008 7:11 AM:
> The test ends up calling sprintf(tmp, "%Ld", -0.0L), but
excuse the typo; I meant "%Lf", not "%Ld"
> the system sprintf does not know how to print -0, so the result is
> 0.00 and lacks -. Does it m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom G. Christensen on 8/9/2008 6:41 AM:
>
> On Irix 6.2 I also see problems in gnulib:
> test-vasprintf-posix.c:1338: assertion failed
> /bin/ksh[10]: 14207 Abort(coredump)
> FAIL: test-vasprintf-posix
>
> The vasprintf-posix problem is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 8/23/2008 10:11 AM:
>>> When stepping through test-frexp with gdb, it fails like this:
>>> (gdb) s
>>> 113 ASSERT (signbit (mantissa));
>> Thanks for the trace. That occurs after the damage is already done; how
On Sun, Sep 07, 2008 at 08:29:44AM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 9/7/2008 4:47 AM:
> > I've spent some time staring at m4s c-stack conftest program and a
> > similar one from libsigsegv and after some trial and error I've isolated
> > a change which will cause the m4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[re-adding bug-gnulib, we are still trying to figure out why
test-c-stack.c fails on Irix 5.3 with libsigsegv 2.6, even though m4's
stack overflow test passed]
According to Tom G. Christensen on 9/7/2008 4:47 AM:
[c-stack.m4 uses a simpler recurse() t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/2/2008 4:50 AM:
>>
>> OK to apply? Are there other files in lib or tests that need matching
>> modifications?
>
> Yes, please apply. 4 test files should be modified in sync:
>
> $ grep -rl 4000d tests/
> tests/test-snp
Eric Blake wrote:
> In looking at this further, it looks like line 4179 of vasnprintf.c should
> _not_ count precision as a prefix if prec_ourselves is nonzero.
Yes. Now that you say it, it's obvious that the code in line 4179 should be
in sync with the code in line 4077.
> Without the patch to v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 8/19/2008 6:29 AM:
> According to Alain Guibert on 8/19/2008 4:40 AM:
>> Sure. There is a segfault on the test for large precisions, on
>> "%.4000d". On libc5 this format works well until "%.1020d", but
>> segfaults for "%.10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/13/2008 12:17 PM:
> Hello Eric,
[please don't top-post]
> > However, I'm still interested in seeing what this does when libsigsegv is
> > not present (you can use './configure --without-libsigsegv-prefix' to
> > rebuild m
On Sat, Aug 23, 2008 at 10:06:29AM -0600, Eric Blake wrote:
> Expected; use './configure --enable-changeword' if you want that feature
> enabled in m4, with the caveat that it will be withdrawn in m4 2.0 (in
> favor of a more powerful and faster changesyntax feature).
Ok, I'll leave it disabled th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 8/23/2008 9:54 AM:
> Hi again!
>
>
> Btw, did I mention last time that m4 tests work, but skip a few?
>
> Skipped checks were:
> ./114.changeword ./115.changeword ./116.changeword ./117.changeword
> ./118.chan
> ge
Hi again!
Btw, did I mention last time that m4 tests work, but skip a few?
Skipped checks were:
./114.changeword ./115.changeword ./116.changeword ./117.changeword ./118.chan
geword ./119.changeword
All checks successful
> According to Thomas Klausner on 8/14/2008 1:21 PM:
> > One failure on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 8/19/2008 6:50 AM:
>
>> SKIP: test-lock
>> SKIP: test-tls
>
> Expected; these tests are only run if you use ./configure --enable-threads
> (generally overkill for m4, since it does not need threading). Bruno, can
> I apply
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 8/14/2008 1:21 PM:
> One failure on NetBSD-4.99.72/amd64:
> test-frexp.c:113: assertion failed
> [1] Abort trap (core dumped) EXEEXT="" EXEEXT...
> FAIL: test-frexp
Thanks for the report. Are you able to help us fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alain Guibert on 8/19/2008 4:40 AM:
> Sure. There is a segfault on the test for large precisions, on
> "%.4000d". On libc5 this format works well until "%.1020d", but
> segfaults for "%.1021d" and above.
Bruno, this looks like a vasnprint
Hello Eric,
On Monday, August 11, 2008 at 20:57:53 -0600, Eric Blake wrote:
> The real problem thus seems to be that the gnulib xvasprintf-posix
> module is not working around this bug in your *printf family of
> functions. Could you post config.log for more details on what
> ./configure determ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 8/15/2008 10:15 PM:
> At any rate, I'm still working on a patch that makes lib/signal.in.h add
> the #define for sa_sigaction if HAVE_SIGACTION &&
> !HAVE_STRUCT_SIGACTION_SA_SIGACTION. I'll post a snapshot for you to try
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom G. Christensen on 8/14/2008 9:03 AM:
> On Wed, Aug 13, 2008 at 08:14:43PM -0600, Eric Blake wrote:
>> According to Tom G. Christensen on 8/13/2008 2:45 PM:
Weird. So Irix 5.3 has sigaction, but not sa_sigaction?
What's sadder is
On Thu, Aug 07, 2008 at 07:37:47AM -0600, Eric Blake wrote:
> I have released a new snapshot from branch-1.4, and hope to release it as
> M4 1.4.12 in the near future. This should fix many of the complaints
> about strtod and other test failures that were reported against 1.4.11.
> However, it als
On Wed, Aug 13, 2008 at 08:14:43PM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 8/13/2008 2:45 PM:
> >>Weird. So Irix 5.3 has sigaction, but not sa_sigaction? Can you please
> >>post the definition of struct sigaction from ?
> >>
> >>From :
> >typedef struct sigaction {
> >
According to Tom G. Christensen on 8/13/2008 2:45 PM:
Weird. So Irix 5.3 has sigaction, but not sa_sigaction? Can you please
post the definition of struct sigaction from ?
From :
typedef struct sigaction {
int sa_flags; /* see below for values */
__si
On Wed, Aug 13, 2008 at 06:05:53AM -0600, Eric Blake wrote:
> According to Tom G. Christensen on 8/9/2008 6:41 AM:
>
> Hello Tom,
>
> |
> | On Irix 6.5.30 I see gnulib test failures:
> | ./test-c-stack.sh[7]: 12954353 Memory fault(coredump)
> | FAIL: test-c-stack.sh
> | FAIL: test-c-stack2.sh
>
Hello Eric,
I build now with --without-libsigsegv-prefix
I attach resulst
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/11/2008 1:51 PM:
| Thanks for your updated reports. It looks like libsigsegv won't help you
| unless you find someone willing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom G. Christensen on 8/9/2008 6:41 AM:
Hello Tom,
Thanks for the report, and sorry for my delay in responding,
|
| On Irix 6.5.30 I see gnulib test failures:
| ./test-c-stack.sh[7]: 12954353 Memory fault(coredump)
| FAIL: test-c-stack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Rick Genter on 8/12/2008 8:23 AM:
| Eric,
|
| Running the tests using 'make -k check' results in the attached log. Two
| tests fail: test-fseeko.sh and test-ftello.sh.
Thanks for the report. Which platform is this on? There are various
Eric,
Running the tests using 'make -k check' results in the attached log.
Two tests fail: test-fseeko.sh and test-ftello.sh.
m4-test-failure.log
Description: Binary data
Rick
--
Rick Genter
[EMAIL PROTECTED]
Hoi,
Test again...
# echo 'define(a,a(a))a' | u:/m4-1.4.11.34-9ecd/src/m4 \
> -L0 -dtx --debugfile=trace
# tail trace
m4trace: -3688- id 7376: a
m4trace: -3689- id 7378: a
m4trace: -3690- id 7380: a
m4trace: -3691- id 7382: a
m4trace: -3692- id 7384: a
m4trace: -3693- id 7386: a
m4trace: -3694- i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/11/2008 1:51 PM:
| Thanks for your updated reports. It looks like libsigsegv won't help you
| unless you find someone willing to port it to your platform.
Actually, according to your logs, libsigsegv did make a difference
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[re-adding gnulib]
According to Alain Guibert on 8/11/2008 3:16 PM:
| Hello Eric, thanks for your support,
|
| On Monday, August 11, 2008 at 7:00:34 -0600, Eric Blake wrote:
|
|> platforms where fopen(file,"a+") opened at the end instead of the
|> b
Hi,
Sorry forgot that to test :(
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/11/2008 9:08 AM:
Thanks for your updated reports. It looks like libsigsegv won't help you
unless you find someone willing to port it to your platform.
|
| Are you in
Hello Bruno,
Ok, thankz for you're answer.
Bruno Haible wrote:
Hi Elbert,
i386-pc-os2-emx | no | no | 2.5
This line simply means that libsigsegv has no support for EMX. This is only
going to change if someone familiar with the EMX API and with a debugger on that
platform is doing the portin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/11/2008 9:08 AM:
Thanks for your updated reports. It looks like libsigsegv won't help you
unless you find someone willing to port it to your platform.
|
| Are you in a position to help debug this? The simplest test woul
Hi Elbert,
> i386-pc-os2-emx | no | no | 2.5
This line simply means that libsigsegv has no support for EMX. This is only
going to change if someone familiar with the EMX API and with a debugger on that
platform is doing the porting work.
Bruno
Hoi Eric,
I build now with Libsigsegv
I attach the logs
Also, it looks like you built without libsigsegv installed. Would you be
willing to download libsigsegv (2.5 is the latest release, although there
are some patches in CVS that have not yet been released, necessary for
correct operation on
Hello Eric, i build Libsigsegv
But with make check i get
Making check in src
make.exe[1]: Entering directory `U:/libsigsegv-2.5/src'
make.exe[1]: Nothing to be done for `check'.
make.exe[1]: Leaving directory `U:/libsigsegv-2.5/src'
Making check in tests
make.exe[1]: Entering directory `U:/libsi
Hi Eric,
To be onnest i have never use any debugging tool or whatever.
And i will see how far i come with the libsigsegv
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/7/2008 12:09 PM:
|
| But with the make -k check there are some errors.
|
| I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 8/10/2008 10:26 PM:
| | Checking ./182.mkstemp
| ...
| | -1
| | +256
|
| Testsuite bug; I'll have to patch doc/m4.texinfo. Basically, I cannot
| assume that a failed 'test -f foo-*' exits with status 1, only that it
| exits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alain Guibert on 8/8/2008 4:13 AM:
Hello, Alain,
I'll reply to different issues with different subject lines, to make it
easier to track.
| | gcc -I. -I../lib -I. -I. -I.. -I./.. -I../lib -I./../lib -g -O2 -c
test-c-stack.c
| | tes
Hoi Eric,
Here is config.log
I try to answer other mails asap :)
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/7/2008 12:09 PM:
|
| But with the make -k check there are some errors.
|
| I attach the check.log
|
| This is with os/2
Thanks for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/7/2008 12:09 PM:
| But with the make -k check there are some errors.
|
| I attach the check.log
|
| This is with os/2
|
Finally, it looks like your system(3) command gives unusual exit statuses
for child processes. I sti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/7/2008 12:09 PM:
| But with the make -k check there are some errors.
|
| I attach the check.log
|
| This is with os/2
|
Second, your platform has a number of SIGFPE on gnulib floating point
replacements. Bruno is more fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Elbert Pol on 8/7/2008 12:09 PM:
|
| But with the make -k check there are some errors.
|
| I attach the check.log
|
| This is with os/2
Thanks for the report. Can you also send your config.log? It looks like
three categories of errors;
On Thu, Aug 07, 2008 at 07:37:47AM -0600, Eric Blake wrote:
> Therefore I would appreciate some feedback
> before making the 1.4.12 release (if you encounter a testsuite failure in
> the m4 suite, please rerun with 'make -k check' before reporting it, so
> that the gnulib testsuite is also run).
>
Hello Eric, Bruno, gentlemen,
On Thursday, August 7, 2008 at 7:37:47 -0600, Eric Blake wrote:
> I would appreciate some feedback before making the 1.4.12 release
With pleasure. My environment: old Linux box (Intel Pentium 200 MMX,
Debian bo, kernel 2.0.40, gcc 2.7.2.1, libc 5.4.33, GNU ld cygnu
Hello Eric,
I run the M4 and the ./configure and make runs fine.
But with the make -k check there are some errors.
I attach the check.log
This is with os/2
Thankz for all :)
check.out.lzma
Description: Binary data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[bcc'ing many of the individuals who reported issues with 1.4.11]
I have released a new snapshot from branch-1.4, and hope to release it as
M4 1.4.12 in the near future. This should fix many of the complaints
about strtod and other test failures tha
56 matches
Mail list logo
