Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 26321 - SELinux bootstrap.sh fails with sandbox error
Summary: SELinux bootstrap.sh fails with sandbox error
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: The Gentoo Linux Hardened Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-10 03:20 UTC by Peter Simons
Modified: 2003-09-09 10:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Simons 2003-08-10 03:20:13 UTC
While installing a new SELinux machine from the scratch, the bootstrap.sh script
failed with a sandbox violation while compiling gcc:

 | root@peti:/tmp$ cat /tmp/sandbox-gcc-3.2.3-r2-30010.log 
 | open_wr:   /ostream-inst.loT

The features setting in /etc/make.conf was:

 | FEATURES="sandbox userpriv usersandbox cvs"


Reproducible: Didn't try
Steps to Reproduce:
Comment 1 Peter Simons 2003-08-10 04:16:58 UTC
I have been able to reproduce the error several times now.

Setting

 | FEATURES="userpriv"

in /etc/make.conf seems to avoid the problem, though.
Comment 2 Martin Schlemmer (RETIRED) gentoo-dev 2003-08-10 13:05:35 UTC
This is usually libtool/configure script being braindead.  Usually the
fix is to make sure that TEMPDIR,TMPDIR, TEMP, TMP, etc is not set before
starting the bootstrap.

Try to add at the top of the bootstrap.sh script:

-----------------------------
TMP="/root/tmp"
TEMP="/root/tmp"
TMPDIR="/root/tmp"
TEMPDIR="/root/tmp"
-----------------------------

It might also be interesting to know if any was set in your
environment ?
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2003-08-24 10:31:16 UTC
No feedback.
Comment 4 Peter Simons 2003-09-09 10:29:19 UTC
I lost access to the machine on which I experienced the bug, so I can't test the solution you proposed any more. Sorry. :-(

I'll be re-installing my system own soon; then I'll report whether this problem still occurs or not.