Summary: | devel/ninja: default config of devel/llvm80 fails to build on bare metal ryzen 5 system | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | aryeh.friedman |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed Unable to Reproduce | ||
Severity: | Affects Only Me | CC: | aryeh.friedman, brooks, mikael |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(brooks) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
aryeh.friedman
2019-07-29 08:21:53 UTC
(In reply to aryeh.friedman from comment #0) oops devel/llvm80 not devel/llvm fails I had the same problem once: the clock on my system wasn't correct. This might be ninja related since the build for graphics/jpeg-turbo went into a similar loop (but gave up after 100 tries) (In reply to mikael.urankar from comment #2) Not in my case it is correct (set it with ntpdate before I started the port installs): root@neomarx:/usr/ports/distfiles # date Mon Jul 29 05:01:15 EDT 2019 root@neomarx:/usr/ports/distfiles # ntpdate pool.ntp.org 29 Jul 05:01:52 ntpdate[563]: adjust time server 108.59.2.24 offset -0.297128 sec (In reply to aryeh.friedman from comment #3) It is for sure related to ninja since I have now had 5 or 6 ports in the xfce4 chain die on the same type of loop with the only commonality between them is they use ninja as their build system... is a default of j 12 on make on a fast processor too fast for ninja? AFACT this isn't an LLVM issue, but rather a ninja issue. There may be a bug here, but I've seen zero other reports and I regularly build llvm with -j32. Closing this since there isn't anything we can work with. |