Re: [PATCH v2] configure: work around compilers that merely warn for unknown options

[Shiz <hi@shiz.me>]

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

> On 28 May 2015, at 06:53, Rob Landley <rob@landley.net> wrote:
> 
> https://github.com/landley/toybox/commit/a913d92bad65
> 
> Specifically the bit about gcc 4.6 warning about the unknown
> -Wno-be-stupid _only_ if it was already producing another warning...
> 
> Rob

I hadn’t, thanks. I’m unsure if there’s a clean way to integrate this
checking quirk in the configure script, since I’m not at all a huge fan of
searching command line output like that: for all you know it might say
something like "-Wno-string-plus-int is going to be the default sometime
in the future" (like Apple LLVM has been known to say for
-Wunused-command-line-argument, coincidentally), and grepping for specific
error messages seems more finicky and/or prone to breakage than anything.

I suppose this is best handled if we happen to come across such a problematic
flag first: no need to optimise for cases that aren’t there yet.

-S

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]