External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-01 17:35:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

maint: allow bootstrap in a sandbox

Browse Source 
Jiri Denemark reported an instance of bootstrapping libvirt
failing when run inside a sandbox, traced to rpm trying to
access /var/ which was not permitted by the sandbox.

Alex Jia reported that 0.9.8-rc1 failed to bootstrap if patch(1)
is not installed.

* bootstrap.conf (buildreq): Avoid rpm call if python-config
exists.  Also, require patch, in case we have gnulib-local diffs.
This commit is contained in:
Eric Blake 2011-12-07 09:26:57 -07:00
parent f21d49144f
commit f48ab7d888
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
bootstrap.conf
View File

@ -195,6 +195,7 @@ gettext 0.17
git 1.5.5 git 1.5.5
gzip - gzip -
libtool - libtool -
patch -
perl 5.5 perl 5.5
pkg-config - pkg-config -
python-config - python-config -
@ -203,10 +204,11 @@ tar -
xmllint - xmllint -
xsltproc - xsltproc -
" "
# You don't have to be on a system with rpm; rather, if you happen to # Use rpm as a fallback to bypass the bootstrap probe for python-config,
# be on RHEL 5, then this bypasses the bootstrap logic that probes for # for the sake of RHEL 5; without requiring it on newer systems that
# a working 'python-config --version'. # have python-config to begin with.
if `(rpm -q python-devel) >/dev/null 2>&1`; then if `(${PYTHON_CONFIG-python-config} --version;
test $? -lt 126 || rpm -q python-devel) >/dev/null 2>&1`; then
PYTHON_CONFIG=true PYTHON_CONFIG=true
fi fi