Bug 236055
| Summary: | lang/gcc8 Linker command failed due to signal | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | drhowarddrfine |
| Component: | Individual Port(s) | Assignee: | freebsd-toolchain (Nobody) <toolchain> |
| Status: | Closed Not A Bug | ||
| Severity: | Affects Only Me | CC: | dim, emaste, marklmi26-fbsd |
| Priority: | --- | ||
| Version: | Latest | ||
| Hardware: | amd64 | ||
| OS: | Any | ||
|
Description
drhowarddrfine
2019-02-26 14:27:02 UTC
There's not much I can do with this report (except to note that it does appear to work for others). Is this reproducible? That is, what happens if you try to build this multiple times? Does it always fail? And always at the same place? Are all dependencies fully up-to-date? Can you rule out a hardware problem (memory,...)? Any other ideas, toolchain@ ? (In reply to Gerald Pfeifer from comment #1) > There's not much I can do with this report (except to note that it does > appear to work for others). ... > Any other ideas, toolchain@ ? At first sight, it looks like the linker ran out of memory. @drhowarddrfine, can you please check your dmesg for messages like "out of swap space"? (In reply to Dimitry Andric from comment #2) Well, yes, as a matter of fact, I was working on my workstation and hadn't checked my email only to find that I am getting messages saying I ran out of swap space. This is a small server so I'm betting that's the issue. Sorry to bother. I wonder if we should add a note to the 'failed unexpectedly' message suggesting the user check for OOM issues etc. (In reply to Ed Maste from comment #4) It would also help if the dmesg/console messages avoided incorrectly referencing "out of swap" when such need not be involved. Details follow, describing the current context. If the person with the problem see any of the: swap_pager_getswapspace(number): failed message they really were out of swap. But if they only see: kernel: pid ... (...), uid ..., was killed: out of swap space they likely had swap available, the issue not really being swap space. The 2nd type of message can happen when there is plenty of swap but processes that stay runnable are preventing having sufficient free RAM after some number of tries by FreeBSD: runnable processes are not (fully) swapped-out by FreeBSD, only paged. In my view the "was killed: out of swap space" should text be adjusted. Other notes: There is a tunable that can increase the number of tries at freeing RAM before "was killed: out of swap space" happens. This is used on low end armv7's and aarch64's and such to allow buildworld and the like to complete with -j4, for example. vm.pageout_oom_seq has a default of 12 (last I checked). Figures like 120 and 1024 have been used on those low end armv7 and aarch64 examples. (pi2 V1.1 and rpi3 are examples: just 1 GiByte of RAM. Of course sufficient swap space is also required for this kind of context.) For lld based links, LDFLAGS.lld+= -Wl,--no-threads can also help avoid memory use by avoiding having ncpu+2 threads in use in each active lld. How-to-build-software documentation should probably cover this subject. |
