At the beginning of the openoffice-2.0.3 build it was concerned that ${PORTAGE_TMPDIR} was less than 5120M, but the build directory is ${PORTAGE_TMPDIR}/portage which is a mount point in my system, so it is getting the test wrong. $PORTAGE_TMPDIR is the default value (/var/tmp), ie not set in /etc/make.conf, but the build stuff actually goes into /var/tmp/portage, which has rather more room on my system. See selected df command results: Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 972404 679708 243300 74% / /dev/hda5 1929068 731688 1099388 40% /var /dev/hdb1 19236308 4294184 13964972 24% /var/tmp/portage
Not an ebuild fault.
Created attachment 91351 [details, diff] eclass/check-reqs.eclass.diff Can you try this patch, please? :)
Doesn't work - get this: * Checking for at least 256MBytes RAM ... [ ok ] * Checking for at least 5120MBytes disk space at ${WORKDIR} ... [ !! ] * Couldn't figure out disk space, skipping ...
Shrug... No idea why ${WORKDIR} wouldn't work.
What is the output of 'df -Pm /var/tmp/portage'?
output of 'df -Pm /var/tmp/portage': Filesystem 1048576-blocks Used Available Capacity Mounted on /dev/hdb1 18786 1457 16376 9% /var/tmp/portage
${WORKDIR} doesn't exist when inside pkg_setup, so Jakub's patch is no good. There doesn't seem to be a neat solution here...
Did run into same problem today. Sorry for creating a dupe of this bug, had opened 176355.
*** Bug 176355 has been marked as a duplicate of this bug. ***
portage folks, this is a CANTFIX until either ${WORKDIR} gets defined in pkg_setup or ${PORTAGE_TMPDIR} really means ${PORTAGE_TMPDIR} and not ${PORTAGE_TMPDIR}/portage.
WORKDIR has no business existing in pkg_* functions use T
while T probably works, the thing that's really needed here is src_check (it only applies at build time, so doesn't really belong in pkg_setup)
(In reply to comment #12) > while T probably works, the thing that's really needed here is src_check (it > only applies at build time, so doesn't really belong in pkg_setup) How about src_unpack? The ebuild could do something like this: src_unpack() { CHECKREQS_DISK_BUILD="2048" check_reqs unpack ${A} }
Well, should work better than pkg_setup at least.
Not much we can do about that (adding new phase functions is beyond the scope of this)
Closing.
Why not just use T? That's got to be better than the status quo..
Will change it to use T.
Committed finally. It now uses $T. Thanks everyone.