On 08/13/2015 05:51 AM, Mark Brown wrote: > On Fri, Jul 10, 2015 at 03:57:40PM -0600, Brett Johnson wrote: > >> gcc5 changes the semantics of inline function declarations, causing some >> inline functions in xemacs to be considered "extern", and thus cause > > In what way does it change the semantics - this seems like a very > surprising and counterintuitive thing to do?
GCC5 now defaults to using the C99 standard, instead of C89. A summary of the changes is given in [1]. Basically in this case, the old "inline" definition is roughly equivalent to a new "extern inline" definition, except that once you declare it "extern", you may now not redefine it in a different TU. I agree that it would be better to make the change in the packaging, rather than in configure.in. If you've already done this, would you mind submitting a patch? [1] https://gcc.gnu.org/gcc-5/porting_to.html -- Brett Johnson <br...@hp.com> "We don't see things as they are, we see them as we are." ~~ Anais Nin
