It's not so clear to me. Here are the relevant lines:
#ifdef __GNUC__ #ifdef __APPLE_CC__ #if ! (__APPLE_CC__ >= 5465 && __STDC_VERSION__ >= 199901L) #define __GMP_EXTERN_INLINE extern __inline__ #define __GMP_INLINE_PROTOTYPES 1 #endif #else /*GNU CC*/ #if defined(__GNUC_STDC_INLINE__) || defined (__GNUC_GNU_INLINE__) #define __GMP_EXTERN_INLINE extern __inline__ __attribute__((__gnu_inline__)) #else #define __GMP_EXTERN_INLINE extern __inline__ #endif #define __GMP_INLINE_PROTOTYPES 1 #endif #endif It looks to me like it should apply the fix to any GCC that is not Apple at precisely the right time. I'll have to have a fiddle on varro. Bill. 2009/2/24 mabshoff <michael.absh...@mathematik.uni-dortmund.de>: > > > > On Feb 24, 8:07 am, Mariah <mariah.le...@gmail.com> wrote: >> Michael, > > Hi Mariah, > >> > > Even if I set SHAREDFLAGS=-fno-common, I get the same failure. >> >> > Ok. I do believe that the fix for inline semantics for OSX does not >> > cover that XCode release. Is this varro? Can you give us gcc -v in >> > either case? >> >> Yes, varro. > > Good, that seemed like the logical choice. > >> varro:~ root# gcc -v >> Using built-in specs. >> Target: powerpc-apple-darwin8.11.0 >> Configured with: /usr/local/gcc-4.3.3/src/gcc-4.3.3/configure --enable- >> languages=c,c++,fortran --with-gmp=/usr/local/gmp-4.2.4/G5-Darwin- >> tiger-gcc-4.3.2-abi32 --with-mpfr=/usr/local/mpfr-2.3.2/G5-Darwin- >> tiger-gmp-4.2.4-gcc-4.3.2-abi32 --prefix=/usr/local/gcc-4.3.3/G5- >> Darwin-tiger-gcc-4.0.1-apple >> Thread model: posix >> gcc version 4.3.3 (GCC) > > Ahh, that explains it since you are using the gcc 4.3.3 you build, not > an Apple provided gcc. > > Bill: I think we can safely assume that any gcc on Darwin needs the > inline semantic fix. > > Thoughts? > >> Mariah > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
