Re: pkg/56336 (m4 fails to build on Solaris 10)

[Eric Blake]

On Wed, Oct 27, 2021 at 09:35:37AM +0900, 箱山洋 wrote:
> Dear m4 developers,
> 
> I found a bug of m4-1.4.19 on Solaris 10 (SPARC), so I sent a bug report to 
> pkgsrc (http://gnats.netbsd.org/56336).
> 
> The message says:
> ./m4: internal error detected; please report this bug to <bug-m4@gnu.org>: 
> Illegal instruction
> 
> So, I also forward the bug report to bug-m4.

Thanks for the report.

>   CC       stackvma.o
> In file included from stackvma.c:1476:0:
> /usr/include/sys/procfs.h:44:2: error: #error "Cannot use procfs in the large 
> file compilation environment"
>  #error "Cannot use procfs in the large file compilation environment"
>   ^
> *** Error code 1
> ...
> 
> This error is similar to the report at 
> https://lists.gnu.org/r/bug-m4/2021-05/msg00020.html
> https://lists.gnu.org/r/bug-m4/2021-05/txtSlhgMVQhua.txt

Indeed, and yet another reason why I need to make time to release m4
1.4.20 with that fix already included.

> m4 was able to built by this patch, but the execution of m4 showed an error:
> 
> # ./m4
> *** stack smashing detected ***:  terminated
> ./m4: internal error detected; please report this bug to <bug-m4@gnu.org>: 
> Illegal instruction
> 
> # /usr/pkgsrc/devel/m4/work/.destdir/usr/pkg/bin/gm4 
> *** stack smashing detected ***:  terminated
> /usr/pkgsrc/devel/m4/work/.destdir/usr/pkg/bin/gm4: internal error detected; 
> please report this bug to <bug-m4@gnu.org>: Illegal instruction

Can you run this under a debugger to get the stack trace of where the
error occurs?

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org