Re: Discussion about why GNU/Linux system upgrades cause old programs to break

Richard Stallman <[email protected]> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > GCC 14 considers certain K&R C constructs an error in C99 mode and
>   > newer, whereas GCC up to 13 merely warned for them in those same modes.
>   > See https://gcc.gnu.org/gcc-14/porting_to.html#warnings-as-errors
>   > including on details how to recover old behavior.
>
> I looked at that page, and found many instances of old practices
> that now cause errors.  These are some examples.
>
>     Implicit int types (-Werror=implicit-int)
>
>     Type checking on pointer types (-Werror=incompatible-pointer-types)
>
>     Implicit function declarations (-Werror=implicit-function-declaration)
>
> What arguments can restore GCC 13 behavior for these cases, and the
> other cases described there?

Per the "Turning errors back into warnings" section [0] of that page,
there are several options, including passing -fpermissive, -std=gnu89,
-std=c89, individual -Wno-error=... or -Wno-..., or in the extreme case,
wrapping the compiler to pass those arguments.

Do you have any suggested tweaks to the phrasing?

[0] https://gcc.gnu.org/gcc-14/porting_to.html#errors-as-warnings

-----BEGIN PGP SIGNATURE-----

iQEBBAEWCgCpFiEEJaa7iN2bdkxrVUHCc4QJ9SDfkZAFAmqFH9IbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25z
Lm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQyNUE2QkI4OEREOUI3NjRDNkI1NTQx
QzI3Mzg0MDlGNTIwREY5MTkwDxxzYW1AZ2VudG9vLm9yZwAKCRBzhAn1IN+RkBPE
AP4iQx9FmRsY+n2bi+SNNoxENK8vBEuLDCInOPB50bbFsAD/XmrV8AgMOIoRER9z
1Ba89fmwYuNwvSLPWjMCc3/kdwA=
=P7Cg
-----END PGP SIGNATURE-----