Re: /usr/X11 vs /opt/X11 on Mountain Lion
Re: /usr/X11 vs /opt/X11 on Mountain Lion
- Subject: Re: /usr/X11 vs /opt/X11 on Mountain Lion
- From: Tim Jenness <email@hidden>
- Date: Mon, 06 Aug 2012 11:10:09 -0700
On Mon, Aug 6, 2012 at 10:46 AM, Jeremy Huddleston Sequoia
<email@hidden> wrote:
On Aug 6, 2012, at 08:38, Tim Jenness <
email@hidden> wrote:
> Can someone confirm for me that the only reason I still have a /usr/X11 in
> Mountain Lion is because I updated from Lion? If I did a fresh install of
> Mountain Lion would I only have /opt/X11 from xquartz?
Yes. It is a symlink. I could have sworn I checked that but I must have been on my lion system when I did.
> I've already had to go
> through and fix include path issues (I think Lion and Snow Leopard must
> have added /usr/X11/include to compiler search paths automatically) and I
> want to make sure that my new binaries work on clean Mountain Lion Macs.
/usr/X11/include was never in any compiler search path automatically. On previous OS versions, /usr/include/X11 existed as a symlink to /usr/X11/include/X11 for backwards compatability with
Ah yes. On lion it's picking up X11 from /usr/include/X11.
Tiger's version of X11. That is probably what you are seeing. You should be using pkg-config to determine CFLAGS for the X11 libraries.
I'm using the autoconf AC_PATH_XTRA macro and I haven't seen any patches to autoconf that use pkg-config (in fact it still uses xmkmf and falls back to using known locations that don't yet include /opt/X11).
Thanks for the clarification.
Now if only I can work out how to compile on ML and get it to work on Lion...
--
Tim Jenness
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden