aterm @1.0.1: fatal error: 'X11/Intrinsic.h' file not found

[dazuelos (dan)]

New install of MacPorts 2.2.0 on /opt/local on Lion (10.8.3) + Xcode (4.6.3) + XQuartz (2.7.4). The X11 include coming with XQuartz are within /opt/X11/include/X11. The MacPorts X11 include files are within /opt/local/include/X11.

WIthin the first one is an Intrinsic.h include. WIthin the last one there is no such include file.

After all the relevant dependencies are already built and installed, the command:

 port -vs build aterm build.jobs=1

gives:

[...]
checking for X... libraries /opt/local/lib, headers /opt/local/include
[...]
/usr/bin/clang -DHAVE_CONFIG_H  -c -pipe -Os -arch x86_64 -Wall -DNO_DEBUG_OUTPUT  -I/opt/local/include -I/opt/local/include     -I/opt/local/include  -I. -I.. -I.  command.c
In file included from command.c:50:
./rxvt.h:142:10: fatal error: 'X11/Intrinsic.h' file not found
#include <X11/Intrinsic.h>      /* Xlib, Xutil, Xresource, Xfuncproto */
         ^
1 error generated.
make[1]: *** [command.o] Error 1
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_aterm/aterm/work/aterm-1.0.1/src'
[...]

The triple use of -I/opt/local/include doesn't seem to be usefull and moreover doesn't point to the right X11 include directory.

How may I help to fix this?

[ryandesign (Ryan Carsten Schmidt)]

You're welcome to use the X11 installed by XQuartz, but by design, MacPorts will only use its own X11, not XQuartz or any other X11 you may have installed elsewhere. The triple -I/opt/local/include is not harmful, so no change needs to me made there. The only problem is that we didn't realize that aterm requires Intrinsic.h, so all we need to do is add a dependency on the port that provides that, which is xorg-libXt.