There are a number of direct uses in acinclude.m4 in GMP. Some are easy to
update (I just did a few). But others are tests to detect bugs in
compilers on esoteric platforms we may not have access to, and adding a
prototype to the function could change things enough that the testcase
would fail
On 8/21/23 11:31, Arsen Arsenović wrote:
Torbjörn Granlund writes:
Dennis Clarke writes:
Pretty sure that should be "int main (void) { return 0; } ".
Surely that is not how the implicit main() declaration looks? A new
compiler warning is warranted. So add (int argc, const char
Torbjörn Granlund writes:
> Dennis Clarke writes:
>
> Pretty sure that should be "int main (void) { return 0; } ".
>
> Surely that is not how the implicit main() declaration looks? A new
> compiler warning is warranted. So add (int argc, const char **argv)!
> Oops, unused parameters, darn.
Dennis Clarke writes:
Pretty sure that should be "int main (void) { return 0; } ".
Surely that is not how the implicit main() declaration looks? A new
compiler warning is warranted. So add (int argc, const char **argv)!
Oops, unused parameters, darn. We need to make a fake dependency on
On 8/20/23 05:48, Torbjörn Granlund wrote:
Niels Möller writes:
I would *not* want to support -Werror as something to be used in general
by users, with arbitrary compiler versions, compile flag tweaks, etc.
Indeed.
There is a fashion among compiler maintainers to accept an ever
Niels Möller writes:
I would *not* want to support -Werror as something to be used in general
by users, with arbitrary compiler versions, compile flag tweaks, etc.
Indeed.
There is a fashion among compiler maintainers to accept an ever
decreasing subset of C, making any effort at producing
Dennis Clarke writes:
> With GMP ver 6.3.0 I run into the same sort of thing :
>
> conftest.c:2:10: error: a function declaration without a prototype is
> deprecated in all versions of C [-Werror,-Wstrict-prototypes]
> int main () { return 0; }
> ^
> void
The configure script
