On Sun, Mar 11, 2018 at 3:42 PM, Uwe Brauer <oub(a)mat.ucm.es&gt; wrote: No, this is due to changes in the C standard. The relevant definition in lisp.h is guarded like this: #if (!defined (__STDC_VERSION__) || __STDC_VERSION__ < 201112L) && \ (!defined (__cplusplus) || __cplusplus < 201103L) /* No type has a greater alignment requirement than max_align_t. (except perhaps for types we don't use, like long double) */ typedef union { struct { long l; } l; struct { void *p; } p; struct { void (*f)(void); } f; struct { double d; } d; } max_align_t; #endif Are you building with sources older than the addition of the #if? -- Jerry James http://www.jamezone.org/

On 2018-03-11, Uwe Brauer <oub(a)mat.ucm.es&gt; wrote: I get that too (Ubuntu 16.04 also), both with my own fork and 21.5.34. On my own fork, I worked round it by adding --cflags='-std=gnu90 -g -O' to the configure command; for 21.5.34 you can do CFLAGS='-std=gnu90 -g -O' bash configure ("-std=gnu90' being the relevant bit) I suppose this is some interaction of C dialect variation and gcc changes, but I haven't found what. (Ubuntu is using gcc 5.4.0 as of now, though I think it was using 4.9.? last time I tried.) Incidentally, ./configure also fails, because configure says #! /bin/sh which these days tells bash to be strictly sh-like, and the sh-like behaviour doesn't have set -o posix which appears somewhere in configure.

Yes indeed, I just pulled the latest tip, but had to apply the specifier patch from Stephen, because otherwise x-symbol does not work. The compilation went smoothly. So the problem is solved.