From 7975d395a2ee0d8b5ba8aa4748c950e9e957503d Mon Sep 17 00:00:00 2001 From: "evan@chromium.org" Date: Wed, 15 Dec 2010 00:44:03 +0000 Subject: seccomp: remove build-time flags Adjusting seccomp through the .gyp file is error-prone and confusing. Instead, because all callers call SeccompSandboxEnabled(), if I want to enable it for some build configuration I can adjust just that function. This change removes all the build-time seccomp configuration and leaves it defaulted off. It should have no change on whether seccomp is enabled. Review URL: http://codereview.chromium.org/5844001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@69208 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/renderer/renderer_main_unittest.cc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'chrome/renderer') diff --git a/chrome/renderer/renderer_main_unittest.cc b/chrome/renderer/renderer_main_unittest.cc index 310e56b..464419b 100644 --- a/chrome/renderer/renderer_main_unittest.cc +++ b/chrome/renderer/renderer_main_unittest.cc @@ -73,12 +73,12 @@ CommandLine RendererMainTest::MakeCmdLine(const std::string& procname, bool debug_on_start) { CommandLine command_line = MultiProcessTest::MakeCmdLine(procname, debug_on_start); -#if defined(USE_SECCOMP_SANDBOX) - // Turn off seccomp for this test. It's just a problem of refactoring, + + // Force seccomp off for this test. It's just a problem of refactoring, // not a bug. // http://code.google.com/p/chromium/issues/detail?id=59376 command_line.AppendSwitch(switches::kDisableSeccompSandbox); -#endif + return command_line; } -- cgit v1.1