[Top][All Lists]

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

Re: M4 assembler error on compile

From: Eric Blake
Subject: Re: M4 assembler error on compile
Date: Thu, 17 Aug 2023 09:57:20 -0500
User-agent: NeoMutt/20230517

Adding bug-gnulib in cc

On Wed, Aug 16, 2023 at 09:47:33PM -0500, Parzival Wolfram wrote:
> I have run into an issue while compiling M4 1.4.19 for Solaris 7 (per GCC's
> configure, target is "i386-unknown-solaris2.7") using GCC 3.2 and Make 4.4.
> Configuring the source tree goes smoothly, but during the make step, the
> following error is generated (truncated to relevant lines):
> make[3]: Entering directory `/staging/stage2/m4-1.4.19/lib`
>   CC asyncsafe-spin.o
> Assembler: asyncsafe-spin.c
>          aline 310        : Illegal mnemonic
>          aline 310        : syntax error
> make[3]: *** [Makefile:2866: asyncsafe-spin.o] Error 1

This file comes from gnulib, so the problem would need to be fixed
there (if it is not already fixed), and then the next release of m4
would depend on newer gnulib.

> I have found no other references to this "aline 310" error at all online, so
> I'm unsure what info is needed to diagnose, or if my build environment is
> even supported in this case, as the only packaged versions of most software
> for Solaris 7 is ancient.

I'm not sure if gnulib is still actively targetting Solaris 7 systems.
It also looks like this particular file was picked up by indirect
dependencies; m4 is single-threaded, so an asynsafe-spin operation is
not going to be vital to performance; you may be able to just #if out
the inline assembly, if we can figure out why gnulib wanted the file
in the first place, without adversely affecting the behavior of the
compiled m4 binary.

> Any assistance is appreciated.

Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]