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

[[[ 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. ]]]

    > In file included from ../src/config.h:1430,
    >                  from sha256.c:23:
    > ./stdio.h:1030:1: error: ‘gets’ undeclared here (not in a function); did you mean ‘fgets’?
    >  1030 | _GL_WARN_ON_USE (gets, "gets is a security hole - use fgets instead");

It looks like this code was trying to do something entirely legitimate:
warn if `gets' is called.  But now that GCC is trying to do the same thing,
one warning warns about setting up the other.  Is that right?

The warning message comes from compiling stdio.h.  Does that mean
that this is a conflict between GCC and Glibc?

Is it possible to make GCC's `gets' warning avoid triggering when the
program sets up a `gets' warning?


-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)