[MacPorts] #57737: clang-3.9 built with clang-3.4 segfaults, but built with clang-3.7 works correctly
MacPorts
noreply at macports.org
Thu Dec 6 23:34:48 UTC 2018
#57737: clang-3.9 built with clang-3.4 segfaults, but built with clang-3.7 works
correctly
------------------------+----------------------
Reporter: kencu | Owner: jeremyhu
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: clang-3.9 |
------------------------+----------------------
Comment (by kencu):
I rebuilt clang-3.9 with clang-3.4 and will attach the full build log, for
any interest there may be there. Still segfaults with any use.
{{{
$ /opt/local/bin/clang-mp-3.9 -c ken_os_version_check_clang-6.c
clang: error: unable to execute command: Bus error
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 3.9.1 (tags/RELEASE_391/final)
Target: i386-apple-darwin9.8.0
Thread model: posix
InstalledDir: /opt/local/libexec/llvm-3.9/bin
clang: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed
source, and associated run script.
clang: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg:
/var/folders/JS/JSmhNUB9HNSSCVaN+wE+XU+++TI/-Tmp-/ken_os_version_check_clang-6-af0b3d.c
clang: note: diagnostic msg:
/var/folders/JS/JSmhNUB9HNSSCVaN+wE+XU+++TI/-Tmp-/ken_os_version_check_clang-6-af0b3d.sh
clang: note: diagnostic msg:
}}}
The blacklisting in the clang-3.9 Portfile already excludes clang-3.4, but
as all the compilers are blacklisted, it winds up circling back to
`gcc-4.2` on Leopard, which of course fails as it is not c++11.
I'm not 100% certain we can automate this fully, but we could add
clang-3.7 as a fallback compiler in the clang-3.9 Portfile.
The LibcxxOnOlderSystems instructions already lead people to clang-3.4 and
then clang-3.7, and then beyond, so if they follow those instructions,
they should be good.
--
Ticket URL: <https://trac.macports.org/ticket/57737#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list