Bug 234125 - devel/llvm60: Not building in FreeBSD 12.0-RELEASE
Summary: devel/llvm60: Not building in FreeBSD 12.0-RELEASE
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Brooks Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-18 09:34 UTC by Gerard Seibert
Modified: 2019-01-17 19:19 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (brooks)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerard Seibert 2018-12-18 09:34:25 UTC
uname -a
FreeBSD scorpio.seibercom.net 12.0-RELEASE FreeBSD 12.0-RELEASE r341666 GENERIC  amd64

After updating to FreeBSD 12.0-RELEASE, I attempted to rebuild my installed ports. The "devel/llvm60" port failed. This is from the end of the build log:

c++: error: unable to execute command: Killed
c++: 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: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin
c++: 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.
c++: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/RedundantVoidArgCheck-28ee29.cpp
c++: note: diagnostic msg: /tmp/RedundantVoidArgCheck-28ee29.sh
c++: note: diagnostic msg: 

********************
ninja: build stopped: subcommand failed.
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/llvm60
=>> Cleaning up wrkdir
===>  Cleaning for llvm60-6.0.1_4
build of devel/llvm60 | llvm60-6.0.1_4 ended at Tue Dec 18 02:51:32 EST 2018
build time: 09:19:35
!!! build failure encountered !!!

The build log is huge; however, I can supply it if necessary.
Comment 1 Brooks Davis freebsd_committer freebsd_triage 2018-12-18 09:43:41 UTC
Given that it's building in the package builders and I've received no other reports, I'm suspicious that it's a resource problem, something related to your /etc/make.conf, or a hardware bug.

Are there any errors in your logs or in dmesg output that mention "c++"?  Is the error reproducible?  How much ram do you have?
Comment 2 Gerard Seibert 2018-12-18 11:46:20 UTC
(In reply to Brooks Davis from comment #1)

At bootup:

real memory  = 5637144576 (5376 MB)
avail memory = 4086706176 (3897 MB)

There is no "c++" mentioned in dmesg

This port built in poudriere before updating to FreeBSD 12.0-RELEASE.

I am not a programmer, but this doesn't look right:

     Target: x86_64-unknown-freebsd12.0

The entire build log is located here:

https://seibercom.net/logs/Building_devel_llvm60.log

There have been no changes to any "make.conf" file since updating to FreeBSD 12.
Comment 3 Brooks Davis freebsd_committer freebsd_triage 2018-12-18 11:59:42 UTC
(In reply to Gerard Seibert from comment #2)

That's not a lot of memory, but I think should be enough.  If other things are building at the same time it might not be.

The Target line is correct for amd64.

I don't test with ccache.  If the failure is reproducible I'd try disabling it and seeing if that fixes the problem.
Comment 4 Brooks Davis freebsd_committer freebsd_triage 2019-01-17 19:19:45 UTC
Without further information there isn't much I can do here.  It works in general so there is almost certainly some subtle local issue.

Thanks for your report.