diff options
author | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-21 18:11:53 +0000 |
---|---|---|
committer | evan@chromium.org <evan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-21 18:11:53 +0000 |
commit | 6ca062724a7e7a571064f53ab73cd37c6031ecfc (patch) | |
tree | b3988ed4f0707e03cc2c00e29082f4e48f4d09b3 /DEPS | |
parent | ff66f9d2b9c224308ef404a63468271d2b110a6a (diff) | |
download | chromium_src-6ca062724a7e7a571064f53ab73cd37c6031ecfc.zip chromium_src-6ca062724a7e7a571064f53ab73cd37c6031ecfc.tar.gz chromium_src-6ca062724a7e7a571064f53ab73cd37c6031ecfc.tar.bz2 |
Pull in a newer version of the seccomp sandbox. Among other things, this gives
us access to fdatasync(), which is needed by SQLite.
It turns out we ran into both a gyp bug (failure to track dependencies for
assembly files) and into a bug in the seccomp sandbox that broke compilation
in release mode (http://codereview.chromium.org/3898005).
BUG=59420
TEST=build Chrome and run with --enable-seccomp-sandbox
Original review: http://codereview.chromium.org/3842004
Review URL: http://codereview.chromium.org/3908006
Third try, TBR.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63384 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
-rw-r--r-- | DEPS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -25,7 +25,7 @@ deps = { (Var("googlecode_url") % "google-url") + "/trunk@147", "src/seccompsandbox": - "http://seccompsandbox.googlecode.com/svn/trunk@119", + "http://seccompsandbox.googlecode.com/svn/trunk@141", "src/sdch/open-vcdiff": (Var("googlecode_url") % "open-vcdiff") + "/trunk@28", |