Kouhei Sutou
kou****@clear*****
2011年 12月 7日 (水) 10:26:56 JST
Hi, In <4EDE3****@fdiar*****> "[groonga-dev, 00647] Re: [PATCH]: Fix configure checking of -Wno-* CFLAGS and CXXFLAGS for GCC" on Tue, 06 Dec 2011 16:44:20 +0100, Kazuhiko <kazuh****@fdiar*****> wrote: > On 06/12/2011 06:51, Arnaud Fontaine wrote: >> This means that if there is no other warning, gcc will not report >> `-Wno-*' warning as an unrecognized command line option. For example if >> you try to compile `int main(void) { return 0; }' with `gcc -o >> /tmp/conftest -g -O2 -Wall -Wextra -Wno-INVALID-OPTION conftest.c', gcc >> will display nothing and exit successfully. >> >> Moreover, gcc 4.3 aborts when there is an unknown command line even >> without `-Werror' (with gcc 4.6.2, only a warning is displayed). >> >> I have attached to this email a patch for configure.ac which checks >> `-WWARNING-FLAG' (which according to GCC manual always raises a warning >> message) when checking `-Wno-WARNING-FLAG'. I have tested it with GCC >> 4.3 and it seems to work well as `-Wno-unused-but-set-variable' is >> properly detected as not available. Could you please consider applying >> this patch if you think it's fine? > > I found that we also have such '-Wno-* ' check in mroonga. So this > change should be also applied in mroonga's configure.ac. I've also fixed it in mroonga. Thanks for your notification! # We may need a mailing list for groonga in English. :-) Thanks, -- kou
