https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220184
--- Comment #14 from Mark Millard <mar...@dsl-only.net> --- (In reply to Chris Collins from comment #11) If this were a general problem the build servers would not be able to build the releases, ports, and such. I do buildworld buildkernel for head on amd64, powerpc64, aarch64, armv7, and powerpc. I've not been having such problems. (I do cross builds amd64 -> <?> more than native but do on occasion build native for the others. My amd64 activity is under virtual box on either Windows 10 or macOS 10.12.5 at this point. The others are directly on the hardware that I have access to.) I build and run non-debug kernels normally despite running versions of head. If what you report was generally happening to others most FreeBSD activity that is clang 4 based would be largely "dead in the water" --but it is not. Almost certainly some uncommon property in other environments is a property of your environment and is involved. The problem is isolating what is involved. It may be time for detailed kernel config specifications. As I remember you already listed the src.config that you use (comment 6). None of my src.conf content matches any of yours. I do not have any 11.x environments at this point, just head based, currently -r320192 . If you have a failing environment that can use a pure GENERIC kernel config and a empty src.conf (or some match to a well established set of such files), you might want to try such. If it happens to work okay then it would form the starting point of a search for what makes the difference. By contrast if things still fail this gets much harder to track down. I can supply examples of my config files if needed but I do not have defaults. (Just using clang 4 for targeting powerpc64 or for powerpc is odd in the first place: I gather evidence of issues that I discover and report them, generally to llvm.) I do have a few source file differences associated with the experiments on non-amd64 --historically mostly tied to powerpc64 and powerpc. (Note: Actually powerpc (32-bit) has problems with crashing even when sitting idle in my context, even if built with gcc 4.2.1. I've had crashes in minutes --or up to somewhat over 10 days 8 hours later. Usually it has been hours but less than 9 hours. But use of clang need not be involved at all for this so it is not a fit to your context. And no other of my environments has shown such behavior so far.) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
