On this particular case, a gcc bug report exists because this specific warning should not show when no other diagnostics are issued. I can't link to the exact report right now but a simple google search should show it. IIRC gcc-4.7 may behave more correctly.
So the correct treatment is either to solve the bug or to use the specialized option to hide it (again, no link : phones are not that goog at multitasking).
Best regards,
-- Emmanuel
Envoyé depuis un mobile Samsung
a écrit :
Hello,
Le lundi 13 février 2012 21:04:53, Nerijus Baliunas a écrit :
> Hello,
>
> I've updated from svn trunk and udpxy package no longer compiles:
>
> mipsel-openwrt-linux-uclibc-gcc -Os -pipe -mips32r2 -mtune=mips32r2
> -fno-caller-saves -fhonour-copts -msoft-float
> -I/a/openwrt/kamikaze/staging_dir/target-mipsel_r2_uClibc-0.9.33/usr/inclu
> de -I/a/openwrt/kamikaze/staging_dir/target-mipsel_r2_uClibc-0.9.33/include
> -I/a/openwrt/kamikaze/staging_dir/toolchain-mipsel_r2_gcc-4.6-linaro_uClib
> c-0.9.33/usr/include
> -I/a/openwrt/kamikaze/staging_dir/toolchain-mipsel_r2_gcc-4.6-linaro_uClib
> c-0.9.33/include -W -Wall -Werror --pedantic -W -Wall -Werror --pedantic
> -DUDPXREC_MOD -DNDEBUG -DTRACE_MODULE -c udpxy.c -o udpxy.o udpxy.c: In
> function 'accept_requests':
> udpxy.c:914:25: error: variable 'rc' set but not used
> [-Werror=unused-but-set-variable] cc1: all warnings being treated as
> errors
>
> Was this change (all warnings being treated as errors) intentional?
Yes, updating the toolchain to gcc-4.6 implies that more warnings are turned
on by default by the compiler.
> Do we
> expect all packages to have no warnings?
Yes, or either selectively build with Wno-error to disable warnings as errors.
Usually these warnings are caused by genuine bugs or unused
variables/functions, so fixing them are beneficial in any case.
--
Florian
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Le lundi 13 février 2012 21:04:53, Nerijus Baliunas a écrit :
> Hello,
>
> I've updated from svn trunk and udpxy package no longer compiles:
>
> mipsel-openwrt-linux-uclibc-gcc -Os -pipe -mips32r2 -mtune=mips32r2
> -fno-caller-saves -fhonour-copts -msoft-float
> -I/a/openwrt/kamikaze/staging_dir/target-mipsel_r2_uClibc-0.9.33/usr/inclu
> de -I/a/openwrt/kamikaze/staging_dir/target-mipsel_r2_uClibc-0.9.33/include
> -I/a/openwrt/kamikaze/staging_dir/toolchain-mipsel_r2_gcc-4.6-linaro_uClib
> c-0.9.33/usr/include
> -I/a/openwrt/kamikaze/staging_dir/toolchain-mipsel_r2_gcc-4.6-linaro_uClib
> c-0.9.33/include -W -Wall -Werror --pedantic -W -Wall -Werror --pedantic
> -DUDPXREC_MOD -DNDEBUG -DTRACE_MODULE -c udpxy.c -o udpxy.o udpxy.c: In
> function 'accept_requests':
> udpxy.c:914:25: error: variable 'rc' set but not used
> [-Werror=unused-but-set-variable] cc1: all warnings being treated as
> errors
>
> Was this change (all warnings being treated as errors) intentional?
Yes, updating the toolchain to gcc-4.6 implies that more warnings are turned
on by default by the compiler.
> Do we
> expect all packages to have no warnings?
Yes, or either selectively build with Wno-error to disable warnings as errors.
Usually these warnings are caused by genuine bugs or unused
variables/functions, so fixing them are beneficial in any case.
--
Florian
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel