Re: [sr #110399] turning off preference for newest supported C?

[Zack Weinberg]

On Thu, Dec 10, 2020 at 6:58 PM Nick Bowler <nbowler@draconx.ca> wrote:>
> On 2020-12-10, Karl Berry <INVALID.NOREPLY@gnu.org> wrote:
> > Anyway. Semantics aside, I had the same reaction to the weird error about
> > "long int". I haven't had a chance to look into it yet, but my expectation
> > is that it is something specific to the TL autoconfigury. (I mean, 
> > presumably
> > int64_t should not be getting #define-d in the first place.)
>
> My guess would be that something is including either <stdint.h> or
> <inttypes.h> with these macros defined.  Per the C spec, int64_t is a
> reserved identifier if either header is included so defining a macro
> with this name and including one of these headers gives undefined
> behaviour.

Karl, if you could repeat one of the failing compilation commands with
`-save-temps -dD` appended to the command line, and then post the `.i`
file that this generates somewhere we can look at it, that might make
it possible for us to help you figure out what went wrong.

zw