Summary: | devel/llvm37: build failure | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Yuri Victorovich <yuri> |
Component: | Individual Port(s) | Assignee: | Brooks Davis <brooks> |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | bapt, miwi |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(brooks) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Yuri Victorovich
![]() ![]() It appears your devel/binutils build is failing to build with gold support. You can either disable the GOLD option in devel/llvm37 or figure out why devel/binutils isn't doing the right thing. GOLD option is "on" by default in devel/llvm37. This makes it a generic problem. It appears that I had too old poudriere jail with version 10.0, that must have had base clang<34. In such case devel/binutil doesn't build ld.gold, and it will break when GOLD=on (which is the default). Since builds for 9.X are also routinely performed, this will probably break llvm37 builds there. Should you make GOLD default in llvm37 in sync with what is the GOLD condition in binutils? Builds work find on 9.3 for amd64 and i386 so long as things aren't too out of date. Ideally I'd make the GOLD option depend on binutils building gold, but no such infrastructure don't seem to exist. What I should probably do is disable the GOLD option by default. You should either make GOLD=off like you said, or copy the condition from binutils, or maybe binutils should lose the clang version check and always build with --enable-gold --enable-plugins. bapt@: Do you think binutils can lose ${COMPILER_VERSION} >= 34 check and make GOLD option a default, or there is some reason not to? llvm37 is gone. |