/var/tmp/portage/openoffice-2.0.2/work/ooo-build-2.0.2/build/OOO_2_0_2/solver/680/unxlngi6.pro/inc/boost/config/compiler/gcc.hpp:67:7: warning: #warning "Unknown compiler version - please run the configure tests and report the results" ../../unxlngi6.pro/slo/eventqueue.o: No space left on device {standard input}: Assembler messages: {standard input}:6537: FATAL: Can't write ../../unxlngi6.pro/slo/eventqueue.o: Illegal seek dmake: Error code 1, while making '../../unxlngi6.pro/slo/eventqueue.obj' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.2/work/ooo-build-2.0.2/build/OOO_2_0_2/slideshow/source/engine make: *** [stamp/build] Error 1 !!! ERROR: app-office/openoffice-2.0.2 failed. This was obviously due to a full harddisk and should have been avoided.
The problem is that we don't really know how much is needed (except a lot)
(In reply to comment #1) > The problem is that we don't really know how much is needed (except a lot) Well, my experience is that anything less than 5 gigs of disk space and 256 megs of RAM just won't make it w/ OO.org-2.0 - but someone could experiment with that with an lvm2 volume (- that shrinks/grows nicely) mounted on /var/tmp and different filesystems and blocks sizes. ;) I asked for this bug to be filed since in every other OO.org bug we ask people - didn't you run out of disk space/memory? Certainly, a minimum requirement to reduce these cases and pointless bugs can be found/estimated with reasonable accuracy.
I agree with jakub on the req's ... I've found just under 5GB to be the minimum, so ensuring that as a minimum should avoid most out-of-space bugs. Compiling with less than 256MB should be possible, but I guess the duration would increase beyond reasonable levels.
(In reply to comment #3) > I agree with jakub on the req's ... I've found just under 5GB to be the > minimum, so ensuring that as a minimum should avoid most out-of-space bugs. > > Compiling with less than 256MB should be possible, but I guess the duration > would increase beyond reasonable levels. > No 256 MB is the real minimum, we received quite a few reports about build breakage when using less. About diskspace: The problem here really is, that it is difficult to have a fixed limit, it varies a lot, in some cases 4 Gigs might be enough, in others 5 might not be sufficient (especially when you build the odk, which I plan to add as a use-flag-option some time soon)
Just added this to the ebuild, setting to 256 MB RAM and 5 Gigs of diskspace, thanks for pointing me to this, hopefully it helps to keep the bug spam low (and me from running into such problems occasionaly ;) )
