- "apt-cache show" is more appropriate for us then
"dpkg --print-avail"
- the test that was supposed to find the correct name for
the nspr and nss libraries didn't work correctly for
distributions (e.g. natty) that for a transition period
included both versions of the library. The new test has
been verified to work with natty.
- it is annoying that the "--clean" option sometimes fails
with a hard-to-understand error message. We now always
use "sudo" to avoid confusing users.
- apart from dbus, some distributions apparently also keep
rsyslogd running after installing the build dependencies.
If this keeps popping up as a problem, we might have to
eventually device a more generic solution.
- when the user told us to remove an old install, try to
remove all traces, instead of just the parts that cost
a lot of disk space.
BUG=none
TEST=verify that we can install natty32bit (with debug symbols) and that afterwards Chrome can be built.
Review URL: https://chromiumcodereview.appspot.com/9764004
git-svn-id: http://src.chromium.org/svn/trunk/src/build@128068 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
script to make them more userfriendly.
In particular, we now recognize systems that have multiple filesystems
(e.g. /home on NFS) and offer to do the right thing.
We also have better support for new Ubuntu distributions (both as
host and as guest). This means, we can now test on "precise".
Added a lot of extra error handling to catch common problems and either
fix them or offer suggestions on how the user can fix them. For example,
we now detect if the user tries to re-install the same chroot environment
multiple times; and we then offer to delete or overwrite the old
installation.
We also detect if a chroot environment is still in active use, and then
refuse to damage it.
In order to help users, who accidentally left an old chroot enviroment
running, we have added a "clean up" option to the wrapper script.
We automatically invoke install-build-deps.sh from install-chroot.sh,
so users only need to run install-chroot.sh and then answer a couple
of questions.
BUG=none
TEST=run install-chroot.sh on a Ubuntu machine and install both lucid32 and precise32. Verify that afterwards, we can build Chrome inside the chroot.
Review URL: https://chromiumcodereview.appspot.com/9702047
git-svn-id: http://src.chromium.org/svn/trunk/src/build@126957 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This fixes a problem on the Chrome buildbots where installing a hardy32 chroot
on a lucid64 machine results in 'ld' and other files in the chroot which do not
work because glibc is too old, and also prevents problems with apt-get fetching
from custom mirrors without source packages.
Review URL: http://codereview.chromium.org/3797014
git-svn-id: http://src.chromium.org/svn/trunk/src/build@63175 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
This fixes a problem where creating a hardy32 chroot fails because the package
name used to be lib64readline5. Perhaps all the packages should be detected
like this, but it can wait until we know if there are other incompatibilities.
Review URL: http://codereview.chromium.org/3775010
git-svn-id: http://src.chromium.org/svn/trunk/src/build@62743 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
james.wei@intel.com
markus@chromium.org
mmoss@chromium.org
mmoss@google.com