[MacPorts] #69754: jed @0.99-19+x11: fatal error: 'X11/Intrinsic.h' file not found; fatal error: 'ft2build.h' file not found (was: jed @0.99-19+x11: fatal error: 'X11/Intrinsic.h' file not found)

[MacPorts]

#69754: jed @0.99-19+x11: fatal error: 'X11/Intrinsic.h' file not found; fatal
error: 'ft2build.h' file not found
----------------------+--------------------
  Reporter:  cfried1  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.9.3
Resolution:           |   Keywords:
      Port:  jed      |
----------------------+--------------------

Comment (by ryandesign):

 Ok thanks, that makes more sense, mostly. Your log shows five attempts to
 install the port. The first two failed with:

 {{{
 .../jed-0.99-19/src/xterm.c:30:11: fatal error: 'X11/Intrinsic.h' file not
 found
 }}}

 After that you presumably installed xorg-libXt which provides
 <X11/Intrinsic.h> because the third attempt failed with a different error
 originating from <X11/Intrinsic.h> so it must have existed:

 {{{
 /opt/local/include/X11/Intrinsic.h:187:10: fatal error: 'X11/Core.h' file
 not found
 }}}

 This should not have happened since <X11/Core.h> is also provided by xorg-
 libXt; it's hard to see how you could have one of the files but not the
 other. The only possibility I can think of is that you were using two
 terminal windows simultaneously and in one you were installing jed and in
 the other you were installing xorg-libXt and by the time that jed went
 looking for <X11/Intrinsic.h> MacPorts had finished extracting
 <X11/Intrinsic.h> from the xorg-libXt archive but hadn't extracted
 <X11/Core.h> yet. I checked our macOS 14 Apple Silicon archive of xorg-
 libXt @1.3.0_0 and it does contain <X11/Intrinsic.h> before <X11/Core.h>.
 (On APFS filesystems, files are not necessarily added to archives in
 alphabetical order.) Still it seems very unlikely since Apple Silicon
 machines have fast SSDs that should be able to extract all of xorg-libXt
 in a fraction of a second. The fourth and fifth attempts failed with:

 {{{
 /opt/local/include/X11/Xft/Xft.h:40:10: fatal error: 'ft2build.h' file not
 found
 #include <ft2build.h>
          ^~~~~~~~~~~~
 }}}

 This is what I now see on my system as well and it's straightforward
 enough: the build system has not added the include path for the directory
 where that file is located (/opt/local/include/freetype). `pkg-config xft
 --cflags` includes the necessary flag, and jed's configure script does use
 that command to discover what flags to use—but only if `pkg-config` is
 found and your log shows:

 {{{
 checking for pkg-config... no
 }}}

 Adding a dependency on pkgconfig is easy. Let me see what else might need
 to be fixed in this port before I commit these fixes.

-- 
Ticket URL: <https://trac.macports.org/ticket/69754#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS