Re: Cannot compile m4 1.4.18 with clang 4.0
Eric Blake <[email protected]>
| Newsgroups | gmane.comp.lib.gnulib.bugs,gmane.comp.gnu.m4.bugs |
|---|---|
| Organization | Red Hat, Inc. |
| Message-ID | <[email protected]> |
On 07/25/2017 03:06 PM, Thompson, KT wrote: > As reported at https://github.com/LLNL/spack/issues/4883, there appears to be a problem compiling m4 (version 1.4.18) on Linux with LLVM clang 4.0. The error is: > > ... > CC m4.o > CC builtin.o > CC debug.o > CC eval.o > CC format.o > CC freeze.o > CC macro.o > CC input.o > CC output.o > CC path.o > CC symtab.o > CCLD m4 > ../lib/libm4.a(xmalloc.o): In function `xnmalloc': > .../m4-1.4.18/lib/xmalloc.c:(.text+0x71): undefined reference to `__muloti4' That appears to be a bug in clang. > > Is there a known work around or patch to resolve this issue? This same version of m4 appears to compile w/o issue for several versions of gcc. I don't know if the bug has already been fixed in gnulib (the provider for xmalloc.c) - if so, then m4 will be fixed the next time we update to newer gnulib and release an updated m4 (which may be sooner rather than later, given that clang is a popular compiler, in spite of the fact that although it is open source, it does not protect your freedoms like gcc). In the meantime, I'm adding gnulib in cc to see if this is a known issue. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
(application/pgp-signature, 619 B)
-----BEGIN PGP SIGNATURE----- Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEEccLMIrHEYCkn0vOqp6FrSiUnQ2oFAll3rVYACgkQp6FrSiUn Q2pyxAgAoHXwRbMngt2jd9p+u/nEgvL0zVlAltyf9pwQismehha7ElK9/8pp1g5m wBFF2ecc6u5RfJhd7xEa5V4jJZUYPNYDysGjRtaASQTNn/A+14ozgy/VAXMnL9qW BQ+c5VC668WkvHctdC1mrRmVlJN9eyCSlW7beY51UT/qego58NpJYzIuG3PqYrhr tQFOwB2mciyNgpN2w20gmO5a2fqgBC28RZjN/M1uYmP2/yLXeqqN43XrXah9Wcfo WsaXpRUqJZJl9GYnVBhO4lt8brvPdbOYPg25iTxEMqg/e0AN6NgMywI4+YmaLAhK b4hsy0BpaNYX79nqMs2v0xm2IadvsQ== =vJMg -----END PGP SIGNATURE-----