Do not tolerate compilation warnings when building libpayload

Make sure the build breaks in case of warnings.

BUG=none

TEST=run the following command with the previous patch removed and
     then restored:

      $ for b in rambi storm nyan_big; do
         cros_workon-$b start libpayload
         emerge-$b libpayload
      done

      all builds succeed with the restored patch and fail when a
      compilation warning is thrown.

Change-Id: I9bdcd8938f59913e4ba86df5e4921b3f821ef920
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/200110
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
This commit is contained in:
Vadim Bendebury 2014-05-15 14:12:54 -07:00 committed by chrome-internal-fetch
commit 16dde87595

View file

@ -57,7 +57,7 @@ CFLAGS = $(EXTRA_CFLAGS) $(INCLUDES) -Os -pipe -nostdinc -ggdb3
CFLAGS += -nostdlib -fno-builtin -ffreestanding -fomit-frame-pointer
CFLAGS += -Wall -Wundef -Wstrict-prototypes -Wmissing-prototypes
CFLAGS += -Wwrite-strings -Wredundant-decls -Wno-trigraphs
CFLAGS += -Wstrict-aliasing -Wshadow
CFLAGS += -Wstrict-aliasing -Wshadow -Werror
$(obj)/libpayload-config.h: $(KCONFIG_AUTOHEADER)
cmp $@ $< 2>/dev/null || cp $< $@