On Wed, Nov 23, 2011 at 01:54:44PM +0700, tknv wrote: > Hello,When I compile armel kernel by gcc4.6 on Linux du > 3.0.0-12-generic-pae #20-Ubuntu SMP Fri Oct 7 16:37:17 UTC 2011 i686 > i686 i386 GNU/Linux. > tknv@du:~$ arm-linux-gnueabi-gcc -v > Using built-in specs. > COLLECT_GCC=arm-linux-gnueabi-gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabi/4.6.1/lto-wrapper > Target: arm-linux-gnueabi > Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro > 4.6.1-9ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr > --program-suffix=-4.6 --enable-shared --enable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix > --with-gxx-include-dir=/usr/arm-linux-gnueabi/include/c++/4.6.1 > --libdir=/usr/lib --enable-nls --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin > --enable-objc-gc --enable-multilib --disable-sjlj-exceptions > --with-arch=armv7-a --with-float=softfp --with-fpu=vfpv3-d16 > --with-mode=thumb --disable-werror --enable-checking=release > --build=i686-linux-gnu --host=i686-linux-gnu --target=arm-linux-gnueabi > --program-prefix=arm-linux-gnueabi- > --includedir=/usr/arm-linux-gnueabi/include > --with-headers=/usr/arm-linux-gnueabi/include > --with-libs=/usr/arm-linux-gnueabi/lib > Thread model: posix > gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > > and Makefile > KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \ > -fno-strict-aliasing -fno-common \ > -Wno-unused-but-set-variable \ > -Wno-unused-parameter \ > -Wno-array-bounds \ > -Wno-format-security \ > -fno-delete-null-pointer-checks > > and make WERROR=0 > but error: array subscript is above array bounds [-Werror=array-bounds] > cc1: all warnings being treated as errors > > How to remove werror all ? > thanks.
Do you know how the compiler is being invoked when compiling the affected file? If not, try make V=1 Where is the code that is triggering the error? If the compiler is raising that error for a good reason, it may be better to improve the code instead of turning of the error check. Cheers ---Dave _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
