From 79b1f3069a7822e36eedf57a7e13833fa559422e Mon Sep 17 00:00:00 2001 From: aszlig Date: Mon, 8 Jul 2013 03:57:23 +0200 Subject: [PATCH] chromium: Unset -Werror in gypFlags. Thanks to @jcumming for notifying me about this in #nixos: 03:47 < jack_c> aszlig: chromium builds with -Werror by default. 03:47 < jack_c> Putting: werror = ""; 03:48 < jack_c> into gypFlags fixes that.. ... 03:52 < jack_c> aszlig: agree -Werror is a good linting tool, but it should probably disabled for distribution. So, I guess it makes sense in our case, especially because different GCC versions will issue different warnings. Signed-off-by: aszlig --- pkgs/applications/networking/browsers/chromium/default.nix | 1 + 1 file changed, 1 insertion(+) diff --git a/pkgs/applications/networking/browsers/chromium/default.nix b/pkgs/applications/networking/browsers/chromium/default.nix index b5557cc1200f..3f072b509945 100644 --- a/pkgs/applications/networking/browsers/chromium/default.nix +++ b/pkgs/applications/networking/browsers/chromium/default.nix @@ -145,6 +145,7 @@ in stdenv.mkDerivation rec { use_cups = cupsSupport; linux_sandbox_path="${libExecPath}/${packageName}_sandbox"; linux_sandbox_chrome_path="${libExecPath}/${packageName}"; + werror = ""; } // optionalAttrs proprietaryCodecs { # enable support for the H.264 codec proprietary_codecs = true;