That's when I imported an updated libintl from gnulib/gettext.
Can you explain what exactly is happening here?
No. It's worked fine on every system I've compiled it on.
Is it an issue with
bash, fortify-headers or anything else?
Since the __extension__ gets inserted by including the fortify-modified
stdlib.h, and __extension__ doesn't appear in relocatable.h, even with
ENABLE_RELOCATABLE defined, I would start there.
Judging from the `gcc -E`
output it looks like preprocessed relocatable.c ends with
__extension__, which is... an error? Is it because `#include_next
<stdlib.h>` produces no output? Why?
Who knows? It seems strange that it wouldn't, since <stdlib.h> is supposed
to define a variety of symbols, and including wchar.h doesn't provide them,
which is one reason you'd expect stdlib.h not to define anything.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/