Граф коммитов

5 Коммитов

Автор SHA1 Сообщение Дата
Tom Anderson c581678b0d Fix build/update-linux-sandbox.sh with POSIX sh
On Debian, the default /bin/sh is dash.  When the chrome_sandbox was built in a
non-component configuration (so no RPATH will be set), the expression:

readelf -d "${CHROME_SANDBOX_BUILD_PATH}" | grep "(RPATH)" &>/dev/null

will have a return code of 0 on dash, but 1 on bash.  This is because ">&" is a
bash feature not available in dash.  This CL changes the expression to ">
/dev/null 2>&1" to be POSIX sh compliant.

R=dpranke

Change-Id: I8c039f57fc47b78b036cf1a30accf8c5fb030055
Reviewed-on: https://chromium-review.googlesource.com/1188756
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#586582}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1a7dfb76d8e4608fc66601f64a09b95da471ab7c
2018-08-28 04:54:31 +00:00
Tom Anderson ee922ea8f8 Require CHROME_DEVEL_SANDBOX to be built with a non-component config
Also:
* Remove an out-of-date comment.
* Add binutils to install-build-deps.sh for readelf and grep.  We already use
  binutils in many places, and it's likely already installed everywhere, but
  it's good to list out direct dependencies.

BUG=850682
R=thakis

Change-Id: I80830ad42fe37f1b93f393f5a6ca5af68ef92998
Reviewed-on: https://chromium-review.googlesource.com/1157436
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#579853}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 2b8a836630dcf0d5c5eba4ecdcc71a5f1ebfb914
2018-08-01 17:41:34 +00:00
isheriff 2a37172e66 Report better error message on update sandbox for gn builds
The documentation for gn builds specifies using a different
output directory than gyp builds, but the update sandbox script
reports error message assuming only gyp builds.

Update the error message to prod user into specifying BUILDTYPE
to find the sandbox in the right place

BUG=

Review URL: https://codereview.chromium.org/1309433002

Cr-Original-Commit-Position: refs/heads/master@{#344600}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: d8807ee10dd5e1e534e46311383c51cc56999f42
2015-08-20 22:39:59 +00:00
mustaq@chromium.org c27c293e6f The sandbox setup script now uses CHROMIUM_OUT_DIR when defined.
BUG=

Review URL: https://codereview.chromium.org/409133006

git-svn-id: http://src.chromium.org/svn/trunk/src/build@285296 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2014-07-24 16:37:20 +00:00
jln@chromium.org 8d14556454 Add update-linux-sandbox.sh to build/
This script is a useful helper to make sure the setuid sandbox is
up-to-date after building Chrome.

BUG=
TEST=
NOTRY=true


Review URL: https://chromiumcodereview.appspot.com/10541017

git-svn-id: http://src.chromium.org/svn/trunk/src/build@140816 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
2012-06-06 20:12:46 +00:00