From 8e8eaf08fb928f90de502c9ee4eb65bbd7ae93d8 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Fri, 21 Jul 2006 22:31:43 +0000 Subject: [PATCH] Make sure that PORTAGE_BUILDDIR exists before attempting to lock it. Depending on the phase, either BUILD_PREFIX or PKG_TMPDIR could be the parent, so we simply use PORTAGE_BUILDDIR to cover both cases. svn path=/main/trunk/; revision=3985 --- pym/portage.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pym/portage.py b/pym/portage.py index fb5bf2c09..447f25c0a 100644 --- a/pym/portage.py +++ b/pym/portage.py @@ -2657,8 +2657,8 @@ def doebuild(myebuild, mydo, myroot, mysettings, debug=0, listonly=0, try: # Build directory creation isn't required for any of these. if mydo not in ["fetch","digest","manifest"]: - portage_util.ensure_dirs( - mysettings["BUILD_PREFIX"], gid=portage_gid, mode=070, mask=02) + portage_util.ensure_dirs(mysettings["PORTAGE_BUILDDIR"], + gid=portage_gid, mode=070, mask=02) builddir_lock = portage_locks.lockdir( mysettings["PORTAGE_BUILDDIR"]) mystatus = prepare_build_dirs(myroot, mysettings, cleanup) -- 2.26.2