Re: m4: internal error detected

[Eric Blake]

On 03/17/2018 03:45 PM, Shanmugasundaram Aruchamy wrote:
> Hi,
> While building from the yocto project on Windows Subsystem for Linux ( Ubuntu
> )
> got the following failure,

> /home/sundar/yocto/poky/build/tmp/work/x86_64-linux/libtool-native/2.4.6-r0/libtool-2.4.6/m4/
> -I
> /home/sundar/yocto/poky/build/tmp/work/x86_64-linux/libtool-native/2.4.6-r0/libtool-2.4.6/tests/
> --force -I m4
> | m4: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >=
> 0' failed.
> | m4: internal error detected; please report this bug to <address@hidden>:

Wow.  That's a failure in your system runtime, and not in m4 proper. 
There's nothing we can do on the m4 list to debug your broken system.  I 
suspect that the bug lies in the Windows Subsystem for Linux, and that 
you'll have to report it there.

> Aborted
> | autom4te: m4 failed with exit status: 2
> | aclocal: error: echo failed with exit status: 2
> | autoreconf: aclocal failed with exit status: 2
> | ERROR: autoreconf execution failed.
>
> Thank you,
> Regards
> SUNDAR

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