https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241848
--- Comment #9 from Robert Clausecker <f...@fuz.su> --- In reply to comment #5 of Mark: That was a -j1 world build with swap enabled. On a separate SSH session, I watched the clang process spike to 1.5 GB (with some 700 MB resident, not sure) before it got killed. I was eventually able to get the compilation to run through by temporarily configuring extra swap space but it was a real pain to do. Please though: I am extremely sure this is a compiler bug or poorly designed program, not a configuration issue. Tweaking VM settings will not solve the underlying issue which is probably a memory leak or something. And if people have to perform arcane tweaks to be able to upgrade their system at all (as no other upgrade path than upgrading from source is supported on ARM32), that's really bad news for people who actually want to run FreeBSD on their ARM boxes. Please solve the underlying issue. I want a solution, not a bandaid. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
