can you see what header defines sa_family_t
and if it has any macro guards

On Tue, 5 Jun 2012 13:36:41 -0500 Peter Fales wrote:
> New build error with this release on our Darwin 10.3 (darwin7.ppc) machine:

> + silent test -d .
> + /bin/cp FEATURE/wait ast_wait.h
> + cc -D_BLD_DLL -dynamic -D_BLD_ast -O2 -I. 
> -I/Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast -Icomp 
> -I/Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/comp 
> -Imisc 
> -I/Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/misc 
> -Iinclude 
> -I/Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/include
>  -Istd 
> -I/Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/std 
> -D_PACKAGE_ast -c 
> /Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/misc/procopen.c
>                                        
> In file included from 
> /Volumes/UFS_exp2/exptools/expmake/build/astsrc/build/src/lib/libast/misc/procopen.c:60:
> /usr/include/sys/socket.h:77: error: parse error before "sa_family_t"
> /usr/include/sys/socket.h:213: error: parse error before "u_char"
> /usr/include/sys/socket.h:216: error: parse error before '}' token
> /usr/include/sys/socket.h:224: error: parse error before "u_short"
> /usr/include/sys/socket.h:238: error: parse error before "u_char"
> /usr/include/sys/socket.h:240: error: _char' undeclared here (not in a 
> function)
> /usr/include/sys/socket.h:242: error: _char' undeclared here (not in a 
> function)
> /usr/include/sys/socket.h:242: error: _char' undeclared here (not in a 
> function)
> /usr/include/sys/socket.h:243: error: parse error before '}' token
> /usr/include/sys/socket.h:376: error: parse error before "u_int"
> /usr/include/sys/socket.h:380: error: parse error before '}' token
> /usr/include/sys/socket.h:471: error: parse error before "u_short"
> /usr/include/sys/socket.h:473: error: parse error before '}' token
> mamake [lib/libast]: *** exit code 1 making procopen.o

_______________________________________________
ast-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-users

Reply via email to