Re: Latest M4 fails M4 checks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 20, 2021 at 7:00 AM Jeffrey Walton <noloader@xxxxxxxxx> wrote:
>
> I'm working on an Apple Mac-mini M1. I installed M4 1.4.18 in /usr/local.
>
> % /usr/local/bin/m4 --version
> zsh: abort      /usr/local/bin/m4 --version
> % /usr/local/bin/m4 -V
> zsh: abort      /usr/local/bin/m4 -V
> <give up>
>
> When I attempt to build/install autotools:
>
> configure:2800: checking for GNU M4 that supports accurate traces
> configure:2855: result: /usr/local/bin/m4
> configure:2858: checking whether /usr/local/bin/m4 accepts --gnu
> configure:2869: result: no
> configure:2880: WARNING: the version of M4 that was found does not support -g
> configure:2882: WARNING: using it with POSIXLY_CORRECT set may cause problems
> configure:2886: checking how m4 supports trace files
> configure:2897: result: --error-output

Here you go:

% sudo lldb /usr/local/bin/m4
(lldb) target create "/usr/local/bin/m4"
Current executable set to '/usr/local/bin/m4' (arm64).
(lldb) r --version
Process 36645 launched: '/usr/local/bin/m4' (arm64)
Process 36645 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
    frame #0: 0x00000001a32f1130 libsystem_kernel.dylib`__abort_with_payload + 8
libsystem_kernel.dylib`__abort_with_payload:
->  0x1a32f1130 <+8>:  b.lo   0x1a32f1150               ; <+40>
    0x1a32f1134 <+12>: pacibsp
    0x1a32f1138 <+16>: stp    x29, x30, [sp, #-0x10]!
    0x1a32f113c <+20>: mov    x29, sp
Target 0: (m4) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x00000001a32f1130 libsystem_kernel.dylib`__abort_with_payload + 8
    frame #1: 0x00000001a32f3a20
libsystem_kernel.dylib`abort_with_payload_wrapper_internal + 104
    frame #2: 0x00000001a32f3a54 libsystem_kernel.dylib`abort_with_payload + 16
    frame #3: 0x00000001a3248864 libsystem_c.dylib`_os_crash_fmt.cold.1 + 80
    frame #4: 0x00000001a31e3e74 libsystem_c.dylib`_os_crash_fmt + 164
    frame #5: 0x00000001a3216aa4 libsystem_c.dylib`__vfprintf + 11604
    frame #6: 0x00000001a323896c libsystem_c.dylib`__v2printf + 404
    frame #7: 0x00000001a321df00 libsystem_c.dylib`_vsnprintf + 264
    frame #8: 0x00000001a3212c58 libsystem_c.dylib`snprintf + 72
    frame #9: 0x000000010002ae08 m4`vasnprintf + 1644
    frame #10: 0x000000010002b34c m4`rpl_vasprintf + 40
    frame #11: 0x0000000100017ee8 m4`xvasprintf + 168
    frame #12: 0x0000000100017fac m4`xasprintf + 28
    frame #13: 0x0000000100002ff0 m4`main + 100
    frame #14: 0x00000001a331df34 libdyld.dylib`start + 4

Maybe it's time to provide an updated M4. A 6 year old version of M4
that crashes is useless.

Jeff




[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux