clang's ". . . and include the . . ." failure informatino vs. poudriere use for port builds

Mark Millard marklmi at yahoo.com
Thu Nov 22 20:22:24 UTC 2018


During a (native) poudriere-devel run I got the following failure. It
appears that poudriere and the (default?) place clang/clang++/. . .
puts evidence of failures (preprocessed source and a script) are not
well matched and the evidence is not in the tar archive produced for
the failure.

[One also has to be careful with kern.corefile definitions in order
to be sure that the core files are in what poudriere captures for
a build failure. Picking kern.corefile=/var/crash/%N.%P.core or
the like is not appropriate for such.]

cc: error: unable to execute command: Abort trap (core dumped)
cc: error: clang frontend command failed due to signal (use -v to see invocation)
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1)
Target: powerpc64-unknown-freebsd13.0
Thread model: posix
InstalledDir: /usr/bin
cc: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed source, and associated run script.
cc: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
cc: note: diagnostic msg: /tmp/vf_convolution-9639c0.c
cc: note: diagnostic msg: /tmp/vf_convolution-9639c0.sh
cc: note: diagnostic msg: 

********************
gmake[1]: *** [ffbuild/common.mak:60: libavfilter/vf_convolution.o] Error 254
gmake[1]: *** Waiting for unfinished jobs....
gmake[1]: Leaving directory '/wrkdirs/usr/ports/multimedia/ffmpeg/work/ffmpeg-4.1'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

This happens to be on powerpc64 where I experiment with using
fairly modern cc/c++ and the like. devel/powerpc64-xtoolchain-gcc
was used for buildworld buildkernel and clang was built as cc.
But the system binutils is from base/binutils . So not an official
gcc 4.2.1 toolchain context.

# uname -apKU
FreeBSD FBSDG5L 13.0-CURRENT FreeBSD 13.0-CURRENT #1 r340287M: Fri Nov  9 19:30:13 PST 2018     markmi at FBSDFSSD:/usr/obj/powerpc64vtsc_xtoolchain-gcc/powerpc.powerpc64/usr/src/powerpc.powerpc64/sys/GENERIC64vtsc-NODBG  powerpc powerpc64 1300003 1300003





===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)



More information about the freebsd-toolchain mailing list