This actually came up sometime in 2007 because of the gcc changes. One solution was in the following thread:
https://gcc.gnu.org/ml/gcc/2007-03/msg01099.html Summarized as: #if defined(__GNUC__) && !defined(__GNUC_STDC_INLINE__) #define ELIDABLE_INLINE extern inline #else #define ELIDABLE_INLINE inline #endif Of course change extern to static for the current problems (apparently there was going to be another change to gcc that would affect 'extern'). On 2016-07-09 15:39, Tom Russo wrote: > On Sat, Jul 09, 2016 at 03:25:16PM -0700, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: >> Bingo! >> >> Now someone who has a lot more brains than me will need to figure out how to >> enforce this change for Cygwin systems... > > Something else to try. > > Replace "inline int" with "static inline int" on those two lines, instead > of removing "inline." Does it still compile on Cygwin? > > If so, then this is something we can do for all systems, without > special-casing Cygwin. > > There was apparently a change in how GCC handles inline functions some > time ago, and perhaps this issue is a reflection of it. That it still > compiles > fine on real operating systems may just be luck. > >> -----Original Message----- >> From: Tom Russo [mailto:[email protected]] >> Sent: Saturday, July 09, 2016 2:20 PM >> >> Perhaps the declaration as inline is what's causing the problem. Try >> removing the inline qualifier from the two function declarations (main.c, >> line 5174 for no_data_selected, and maps.c, line 231 for max_i) and see if >> that helps. >> >> > _______________________________________________ Xastir-dev mailing list [email protected] http://xastir.org/mailman/listinfo/xastir-dev
