On Fri, Oct 28, 2016 at 7:05 AM, Tim Ruehsen <tim.rueh...@gmx.de> wrote:
> Hi,
>
> during some GNU internal discussion I was asked to post my proposal / request
> here.
>
> "I use manywarnings.m4 in my projects which take ~9s here (~25% of the whole
> ./configure run).
> One gcc invocation per (possible) warning options sums up a lot.
>
> gcc -Q --help=warning|awk '{ if ($2 == "[disabled]") print $1 }'
> gives a complete list of available warning options which we can use without
> checking each single option.
> This also takes automatic advantage of new gcc warnings."
>
>
> I took a look at the source but feel somewhat incompetent to provide a patch
> (m4 and shell is just not my competence). It seems to be a pretty low-hanging
> fruit for an expert, though.
>
> I really would enjoy a faster manywarnings.m4 !
Good idea.
Just a matter of someone getting motivated and finding the time.
In the mean time, do you use a ./configure cache?
In day-to-day runs of configure, I rarely notice this, because my
initial invocation of ./configure usually includes e.g.,
`--cache=.cache`.
Of course, if you're always building from a just-unpacked tarball,
that doesn't help. In that case, you can use an absolute name or the
CONFIG_SITE envvar, per
https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Site-Defaults.html.
