Summary: | math/py-numpy: fails to build 11.0 aarch64 due to clang crash (196 ports skipped) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Jan Beich <jbeich> | ||||||
Component: | Individual Port(s) | Assignee: | freebsd-python (Nobody) <python> | ||||||
Status: | Closed Overcome By Events | ||||||||
Severity: | Affects Only Me | CC: | Andrew, dim, emaste, linimon | ||||||
Priority: | --- | Keywords: | needs-patch, needs-qa | ||||||
Version: | Latest | ||||||||
Hardware: | arm64 | ||||||||
OS: | Any | ||||||||
URL: | https://reviews.llvm.org/rL263301 | ||||||||
See Also: | https://bugs.llvm.org/show_bug.cgi?id=26803 | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 201763 | ||||||||
Attachments: |
|
Description
Jan Beich
2017-07-05 14:47:20 UTC
Maybe fixed in FreeBSD 11.1 (clang 4.0) but aarch64 switched to lld which complicates testing due to bug 217189 and bug 214864. Can you please attach the two files dropped in /tmp? E.g. cc: note: diagnostic msg: /tmp/arraytypes-b98a93.c cc: note: diagnostic msg: /tmp/arraytypes-b98a93.sh This builds for me on head with clang 4.0 Created attachment 184912 [details]
numpy/core/src/multiarray/arraytypes.c.src (preprocessed, compressed)
Created attachment 184913 [details]
command line args (for clang 3.8)
So this was known upstream as https://bugs.llvm.org/show_bug.cgi?id=26803, and has been fixed in https://reviews.llvm.org/rL263301. Since 11-STABLE now has clang 4.0.0, and head has 5.0.0, which both include this fix, I don't think there is much that can be done at this point? Can/should the port build with an affected version of clang from ports until all supported releases contain the fix? (In reply to Kubilay Kocak from comment #7) IMO it's fine if someone wants to add to the port's Makefile to have it use a Clang port/package if the system clang is too old, but it's not necessary. It is reasonable to expect users will at least track more recent release for a newly-developing architecture like this. (In reply to Ed Maste from comment #8) The main reason to support 11.0 with arm64 is that's what portmgr targets when building packages. (In reply to Andrew Turner from comment #9) Ah yes, good point. Perhaps setting USES=compiler:c++14-lang for arm64 could be a suitable workaround? 11.0's EOL is in a couple of weeks. If nobody wants to apply the c++14-lang workaround we can just close this as OBE soon. 11.0 EOL'd, builds fine on other releases. http://thunderx1.nyi.freebsd.org/data/latest-per-pkg/py27-numpy/1.13.3%2C1/ |