The short story (after much long effort following up other leads related to fink conflicts, apparent broken dports synchronization, etc.) is that I had a bad tclConfig.sh unknowingly installed in /usr/ local/lib. Grrr. It's too bad that there's not a more bulletproof way of ensuring that the right tcl is being used because several posts in the archives and bug reports ultimately relate to tcl conflicts. Case closed. On Apr 17, 2007, at 4:16 PM, David Kulp wrote:
I can't run "port selfupdate" on a fresh install of 1.4. It fails when building Pextlib, complaining about socket.h.
Anyone have a clue? I've searched the list archives and found nothing similar.
Thanks in advance, -d
===> making all in src/pextlib1.0 gcc -c -DUSE_TCL_STUBS -g -O2 -W -Wall -pedantic -g -Os - DHAVE_CONFIG_H -I.. -I. -I"/usr/include" -DHAVE_UNISTD_H=1 - DHAVE_LIMITS_H=1 -DTCL_WIDE_INT_TYPE=long\ long -DWORDS_BIGENDIAN=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 - DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 - DNO_VALUES_H=1 -DNO_DLFCN_H=1 -DHAVE_UNISTD_H=1 - DHAVE_SYS_PARAM_H=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 - DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 - DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 - DSTDC_HEADERS=1 -Dsocklen_t=unsigned -DHAVE_SIGNED_CHAR=1 - DHAVE_PUTENV_THAT_COPIES=1 -DHAVE_SYS_IOCTL_H=1 - DHAVE_SYS_FILIO_H=1 -fno-common Pextlib.c -o Pextlib.o In file included from Pextlib.c:96: /usr/include/sys/socket.h:99: error: two or more data types in declaration specifiers make[2]: *** [Pextlib.o] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1