On 5/29/21 3:20 PM, Kiyoshi KANAZAWA wrote:
Thank you, Paul.
Everything good with your patch in 32 bit mode on Solaris.
By the way, is this patch valid only in 32 bit mode (on Solaris) ?
The patch should have no effect in 64-bit mode, which should work
regardless of whether the patch is inst
Paul Eggert wrote:
> Thanks for reporting the bug. Please try the attached patch, which I
> installed into Gnulib.
Thanks, Paul, that's the correct fix.
Apologies: I had tested the 'sigsegv' module mostly on its own, and
tested it together with GNU m4 only on 4 or 5 platforms.
Bruno
Thank you, Paul.
Everything good with your patch in 32 bit mode on Solaris.
By the way, is this patch valid only in 32 bit mode (on Solaris) ?
make & make check pass without the patch in 64 bit mode (./configure CC='gcc
-m64').
--- Kiyoshi
Thanks for reporting the bug. Please try the attached patch, which I
installed into Gnulib.
stackvma.c says it contains simplified copies of code in vma-iter.c,
which didn't have this bug. Bruno, am I right in guessing that there are
two files mainly because libsigsegv was separate from Gnulib
On Sat, May 29, 2021 at 05:06:00AM -0500, Hanspeter Niederstrasser wrote:
> Hello,
>
> I'm not on Haiku, but on macOS 10.14.6 and am having a similar test failure
> with m4-1.4.19 and 198.sysval:
>
> Checking ./197.sysval
> Checking ./198.sysval
> @ ../doc/m4.texi:6751: Origin of test
> ./198.sys
On Sat, May 29, 2021 at 08:33:08AM +0900, Kiyoshi KANAZAWA wrote:
> Hello,
>
> Trying to install m4-1.4.19 on Solaris 11.3 x86.
>
> $ uname -a
> SunOS hidden 5.11 11.3 i86pc i386 i86pc
>
> $ gcc --version
> gcc (GCC) 10.3.0
>
> $ ./configure CC=gcc
> (it mean CC='gcc -m32')
>
> $ make
> :
>
Hello,
I'm not on Haiku, but on macOS 10.14.6 and am having a similar test
failure with m4-1.4.19 and 198.sysval:
Checking ./197.sysval
Checking ./198.sysval
@ ../doc/m4.texi:6751: Origin of test
./198.sysval: stderr mismatch
--- m4-tmp.38611/m4-xerr2021-05-29 04:47:35.0 -0500
FSF copyright is Ok for me, I've been contributing to free software before
(fvwm2 & emacs/gnus).
For my company, it's in the mutual interest as well.
Well, I'd do the sensible thing and reduce the amount of #line output - and
especially suppress it after line-continuation backslashes, where it's
