Re: inline related build failures on MacOS X 10.5

2008-04-12 Thread Bruno Haible
Ralf Wildenhues cited me: > > This should ideally be solved through autoconf (let autoconf try > > "-std=gnu99 -D__GNUC_STDC_INLINE__" instead of "-std=gnu99") Actually, autoconf should define __GNUC_STDC_INLINE__ together with "-std=gnu99" *only* if the compiler is an __APPLE_CC__ >= 5465. It mus

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Bruno Haible
Peter O'Gorman wrote: > It is unlikely that there will be a version of gcc from Apple based on > gcc-4.3 or later (because Apple is currently not introducing any GPLv3 > software). Currently... They will have to buy into gcc 4.3 or newer in the long run. > Note that what will become Xcode-3.1 see

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Bruno Haible
Ludovic Courtès wrote: > but (i) "static inline" is safe, Yes sure. > (ii) who knows what silly > patches Apple will apply to their next GCC series, and (iii) let's not > put too much effort into systems that deliberately break things. I don't think this is fair towards Apple. The GCC developers

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Peter O'Gorman
Bruno Haible wrote: > Ludovic Courtès wrote: >> FWIW, I solved it this way in Guile, based on what GNU R does: >> >> >> http://git.sv.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=7dc9ae7179b8b099897f8080b675e2a9c54d388c > > Do you have information about the compilers with build numbers 5401..5464

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Ralf Wildenhues
Hello, I haven't followed the discussion at all, but: * Bruno Haible wrote on Fri, Apr 11, 2008 at 03:14:07PM CEST: > > This should ideally be solved through autoconf (let autoconf try > "-std=gnu99 -D__GNUC_STDC_INLINE__" instead of "-std=gnu99"), but since I > don't know when the next autoconf

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Ludovic Courtès
Hi, Bruno Haible <[EMAIL PROTECTED]> writes: > Ludovic Courtès wrote: >> FWIW, I solved it this way in Guile, based on what GNU R does: >> >> >> http://git.sv.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=7dc9ae7179b8b099897f8080b675e2a9c54d388c > > Do you have information about the compilers wi

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Bruno Haible
Ludovic Courtès wrote: > FWIW, I solved it this way in Guile, based on what GNU R does: > > > http://git.sv.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=7dc9ae7179b8b099897f8080b675e2a9c54d388c Do you have information about the compilers with build numbers 5401..5464 ? Btw, when the next versio

Re: inline related build failures on MacOS X 10.5

2008-04-11 Thread Ludovic Courtès
Hi, Bruno Haible <[EMAIL PROTECTED]> writes: > $ gcc -v 2>&1 | tail -1 > gcc version 4.0.1 (Apple Inc. build 5465) > > It appears to be a GCC 4.0.x with some backports from the GCC 4.2 and 4.3 > development. > > For 'extern inline', this gcc generates a symbol with global visibility in > "gcc

inline related build failures on MacOS X 10.5

2008-04-11 Thread Bruno Haible
On MacOS X 10.5.2, GNU cpio-2.9 and GNU tar-1.18 exhibit build failures. This is for cpio: gcc -std=gnu99 -g -O2 -o cpio copyin.o copyout.o copypass.o defer.o dstring.o global.o main.o tar.o util.o filemode.o idcache.o makepath.o userspec.o ../lib/libcpio.a -L/Users/bruno/data/local-macos