https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206679
--- Comment #2 from Mark Millard <[email protected]> --- 6GBytes of RAM, 2 GByte of swap. 64GByte of disk. But ZFS (as an experiment) so the file system likely is more memory hungry than if I'd used UFS. I do not remember top showing it being nearly out of memory but I'll have to retry at some point if I want to be sure. I would have guessed that the file format has some 4GB limit that might have been reached, explaining why the terminology reads like a file truncation instead of out-of-memory. Looking around some I found one 2012 reference to code in ar that was reported to then look like: /* Catch an attempt to grow an archive past its 4Gb limit. */ if (archive_member_file_ptr != (file_ptr) offset) { bfd_set_error (bfd_error_file_truncated); return FALSE; } If this was the issue it might imply needing the library to be split up in order to fit for what is now qt's debug/libWebCore.a builds. Looks like you are right about WITH_DEBUG= : the WITH_DEBUG= is some stray text that should not be in my make.conf . share/mk/*'s (bsd.lib.mk and bsd.prog.mk) use the following sort logic to add -g: .if ${MK_DEBUG_FILES} != "no" && empty(DEBUG_FLAGS:M-g) && \ empty(DEBUG_FLAGS:M-gdwarf-*) CFLAGS+= -g CTFFLAGS+= -g .endif And that is the only reason that I can think of for the WITH_DEBUG= existing. So I'll remove it but still use WITH_DEBUG_FILES= and see what happens. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ kde-freebsd mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
