On Sep 16, 2004, at 10:42 PM, Ben Collins-Sussman wrote:
>
> /bin/sh /Users/sussman/projects/svn/libtool --silent --mode=compile 
> gcc -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp  -g -g 
> -Wall -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations 
> -DNEON_ZLIB -DNEON_SSL -DSVN_DEBUG -DAP_DEBUG -Wpointer-arith 
> -Wwrite-strings -Wshadow -std=c89   -I./subversion/include 
> -I./subversion -I/usr/local/include/neon -I/usr/local/apache2/include  
>  -I/usr/local/apache2/include -I/usr/local/BerkeleyDB.4.2/include  -o 
> subversion/libsvn_subr/io.lo -c subversion/libsvn_subr/io.c
> In file included from /usr/include/libkern/OSByteOrder.h:35,
>                  from /usr/include/architecture/byte_order.h:34,
>                  from /usr/include/mach-o/loader.h:47,
>                  from /usr/include/mach-o/dyld.h:34,
>                  from /usr/local/apache2/include/apr_portable.h:162,
>                  from subversion/libsvn_subr/io.c:48:
> /usr/include/libkern/ppc/OSByteOrder.h:42: error: syntax error before 
> "uint16_t"
> /usr/include/libkern/ppc/OSByteOrder.h:57: error: syntax error before 
> "uint32_t"
> /usr/include/libkern/ppc/OSByteOrder.h:72: error: syntax error before 
> "uint64_t"
> /usr/include/libkern/ppc/OSByteOrder.h:93: error: syntax error before 
> "void"
> /usr/include/libkern/ppc/OSByteOrder.h:107: error: syntax error before 
> "void"
> /usr/include/libkern/ppc/OSByteOrder.h:121: error: syntax error before 
> "void"
> /usr/include/libkern/ppc/OSByteOrder.h:143: error: syntax error before 
> "uint16_t"
> /usr/include/libkern/ppc/OSByteOrder.h:153: error: syntax error before 
> "uint32_t"
> /usr/include/libkern/ppc/OSByteOrder.h:163: error: syntax error before 
> "uint64_t"
>
Well, googling for this error led to an interesting discovery.
At this link:
   http://forums.macosxhints.com/archive/index.php/t-19270
...it's suggested that these errors are happening in the kernel headers 
whereever things are declared 'inline', and that this is incompatible 
with gcc 3.3's -ansi option.
Sure enough, if I remove our '-std=c89' option from the compile line 
above, then io.c compiles just fine.
This is perplexing to me.  I don't think Subversion is doing anything 
wrong, is it?  Is this perhaps some sort of bug in the latest OSX GNU 
toolchain?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 17 14:55:36 2004