[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150528051119.GR17573@brightrain.aerifal.cx>
Date: Thu, 28 May 2015 01:11:19 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH v2] configure: work around compilers that merely
warn for unknown options
On Thu, May 28, 2015 at 01:53:44PM +0900, Rob Landley wrote:
> On Thu, May 28, 2015 at 12:52 PM, Shiz <hi@...z.me> wrote:
> > some compilers (such as clang) accept unknown options without error,
> > but then print warnings on each invocation, cluttering the build
> > output and burying meaningful warnings.
>
> You saw this already, right?
>
> https://github.com/landley/toybox/commit/a913d92bad65
I hadn't seen it yet.
> Specifically the bit about gcc 4.6 warning about the unknown
> -Wno-be-stupid _only_ if it was already producing another warning...
musl makes a lot less assumptions about compiler command-line though;
since we have a configure script, we just test every option we want to
use that's not completely standard. The problem this patch addressed
(BTW, it's now committed) is that some compilers broke these tests by
failing to report an error for unsupported options.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
