Only masochists use MacPorts GCC ...

MacPorts builds of GCC remove /usr/local and add /opt/local (or maybe the MacPorts prefix, which need not be /opt/local) to the "system" include path of GCC. This wouldn't be a big deal, except that GCC in its infinite wisdom enforces the "system-ness" and will not allow you to increase the priority of the system directories (unless you forgo all built-in directories with -nostdinc). Specifically, /usr/X11R6/include is *not* a system include directory by default. This means that it will always shadow /opt/local/include, and thus a MacPorts GCC will find Apple-provided versions of headers for Xft (in Tiger, v2.1.0) and fontconfig (v1.0.2) pretty much no matter what you do, even though MacPorts itself provides versions of both libraries (currently, v2.1.7 for Xft and v2.4.2 for fontconfig). The version lag is bad enough, but worse is that the linker finds the MacPorts libraries and links them in! Of course, fairly shortly the s hits the f, and down you go. I don't know if this affects anything else, but if you're building with Xft/fontconfig, you are well-advised to avoid MacPorts builds of GCC. Patchs for configure to at least warn of this problem would be welcome. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta