This workaround is no longer needed as of about a year ago, so killing it off.
authorJeremy Huddleston <eradicator@gentoo.org>
Fri, 14 Oct 2005 07:16:28 +0000 (07:16 +0000)
committerJeremy Huddleston <eradicator@gentoo.org>
Fri, 14 Oct 2005 07:16:28 +0000 (07:16 +0000)
profiles/default-linux/amd64/profile.bashrc [deleted file]
profiles/default-linux/sparc/sparc64/dev/multilib/profile.bashrc [deleted file]

diff --git a/profiles/default-linux/amd64/profile.bashrc b/profiles/default-linux/amd64/profile.bashrc
deleted file mode 100644 (file)
index b732806..0000000
+++ /dev/null
@@ -1,26 +0,0 @@
-# fix for bug 60147, "configure causes sandbox violations when lib64
-# is a directory". currently only works with cvs portage.
-#SANDBOX_WRITE="${SANDBOX_WRITE}:/usr/lib64/conftest:/usr/lib64/cf"
-addwrite /usr/lib64/conftest
-addwrite /usr/lib64/cf
-
-# oh goodie, yet ANOTHER sandbox bug!!!! >:|
-# without portage 2.0.51 and the following entries, at least dbus will spew
-# sandbox violations like mad with python in lib64.
-addpredict /usr/lib64/python2.0/
-addpredict /usr/lib64/python2.1/
-addpredict /usr/lib64/python2.2/
-addpredict /usr/lib64/python2.3/
-addpredict /usr/lib64/python2.4/
-addpredict /usr/lib64/python2.5/
-addpredict /usr/lib64/python3.0/
-
-# sandbox is disabled for /dev/null by default, so this bug isnt caught.
-# hopefully this will help us figure out where this problem occurs...
-if [ ! -e /dev/null ] ; then
-       eerror "/dev/null doesnt exist! this is bad! tail -n 20 /var/log/emerge.log and attach the output to http://bugs.gentoo.org/show_bug.cgi?id=65876"
-       exit 1
-elif [ -f /dev/null ] ; then
-       eerror "/dev/null is a normal file! this is bad! tail -n 20 /var/log/emerge.log and attach the output to http://bugs.gentoo.org/show_bug.cgi?id=65876"
-       exit 1
-fi
diff --git a/profiles/default-linux/sparc/sparc64/dev/multilib/profile.bashrc b/profiles/default-linux/sparc/sparc64/dev/multilib/profile.bashrc
deleted file mode 100644 (file)
index 7c29988..0000000
+++ /dev/null
@@ -1,20 +0,0 @@
-# lib64 sandbox stuff copied from amd64's profile.bashrc:
-# fix for bug 60147, "configure causes sandbox violations when lib64
-# is a directory". currently only works with cvs portage.
-
-addwrite /usr/lib64/conftest
-addwrite /usr/lib64/cf
-
-# oh goodie, yet ANOTHER sandbox bug!!!! >:|
-# without portage 2.0.51 and the following entries, at least dbus will spew
-# sandbox violations like mad with python in lib64.
-addpredict /usr/lib64/python2.0/
-addpredict /usr/lib64/python2.1/
-addpredict /usr/lib64/python2.2/
-addpredict /usr/lib64/python2.3/
-addpredict /usr/lib64/python2.4/
-addpredict /usr/lib64/python2.5/
-addpredict /usr/lib64/python3.0/
-
-export CFLAGS_sparc32
-export CFLAGS_sparc64