[MacPorts] #40680: aterm @1.0.1: fatal error: 'X11/Intrinsic.h' file not found

[MacPorts]

#40680: aterm @1.0.1: fatal error: 'X11/Intrinsic.h' file not found
-----------------------------+--------------------------
  Reporter:  dan+macports@…  |      Owner:  ryandesign@…
      Type:  defect          |     Status:  assigned
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.2.0
Resolution:                  |   Keywords:
      Port:  aterm           |
-----------------------------+--------------------------

Comment (by dan+macports@…):

 Replying to [comment:4 ryandesign@…]:
 [...]
 > So I guess there is some kind of opportunistic linking going on. I
 should compare the log from the buildbot with the one from my system to
 see if I can determine what it is.

 I agree with this analysis and try to locate what may interfere.
 On my system, `XQuartz` is installed, and `Intrinsic.h` is found within
 `/opt/X11/include/X11` (which is also by the way of symbolic links
 `/usr/X11/include/X11`).

 During the `Xquartz` install 2 symbolic links are created:
 {{{
 % ls -ld X11*
 lrwxr-xr-x  1 root  wheel  8 Oct  3 14:04 X11 -> /opt/X11
 lrwxr-xr-x  1 root  wheel  8 Oct  3 14:04 X11R6 -> /opt/X11
 %
 }}}
 Since I haven't yet installed a full X11 on `MacPorts`, my PATH does
 contain the `XQuartz` X11
 binary PATH '''before''' the `MacPorts` binary PATHes.
 {{{
 % echo $PATH
 /bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin:/local/bin:/opt/local/bin:/opt/local/sbin
 %
 }}}
 On a correct build on Mountain Lion, what is the PATH of `Intrinsic.h`?

-- 
Ticket URL: <https://trac.macports.org/ticket/40680#comment:5>
MacPorts <http://www.macports.org/>
Ports system for OS X