Configure: make --strict-warnings a regular user provided compiler option
authorRichard Levitte <levitte@openssl.org>
Thu, 14 Feb 2019 15:26:40 +0000 (16:26 +0100)
committerRichard Levitte <levitte@openssl.org>
Thu, 28 Feb 2019 12:08:04 +0000 (13:08 +0100)
commitcd7dc67c4460947b6139cd08bc23a84e3d8bb429
treea7c8605252d18bec57e101db563ab34178ed6088
parentdbb1340314fcec37662d79720e6566fdd5a232e8
Configure: make --strict-warnings a regular user provided compiler option

This makes `--strict-warnings` into a compiler pseudo-option, i.e. it
gets treated the same way as any other compiler option given on the
configuration command line, but is retroactively replaced by actual
compiler warning options, depending on what compiler is used.

This makes it easier to see in what order options are given to the
compiler from the configuration command line, i.e. this:

    ./config -Wall --strict-warnings

would give the compiler flags in the same order as they're given,
i.e.:

    -Wall -Werror -Wno-whatever ...

instead of what we got previously:

    -Werror -Wno-whatever ... -Wall

(cherry picked from commit fcee53948b7f9a5951d42f4ee321e706ea6b4b84)

Reviewed-by: Paul Dale <paul.dale@oracle.com>
(Merged from https://github.com/openssl/openssl/pull/8359)
Configure