Re: Emacs Mac port

[Aaron Madlon-Kay]

(Resending to list as well; apologies to Mr. Yamamoto.)

> It is supposed to build without /usr/include

My understanding is that it's not /usr/include that was the problem,
but rather headers in /System/Library/Frameworks and
/System/Library/PrivateFrameworks that were bad. The High Sierra CLI
tools package installs these, whereas the Mojave package does not,
thus requiring macOS_SDK_headers_for_macOS_10.14.pkg to fix.

> You seem to use MacPorts rather than Homebrew.  Could you send me the
> exact error messages when building the Mac port after temporary
> renaming /usr/include to some other name?

macOS's SIP (https://en.wikipedia.org/wiki/System_Integrity_Protection)
prevents me from merely renaming /usr/include, and it's a pain to turn
on and off, so I apologize but I'm not willing to do this.

> Also, please show me the output of the following commands:

Sure:

$ pkg-config --cflags --libs "libxml-2.0 > 2.6.17"
-I/opt/local/include/libxml2 -L/opt/local/lib -lxml2
$ pkg-config --variable pcfiledir "libxml-2.0 > 2.6.17"
/opt/local/lib/pkgconfig

(MacPorts as a rule requires dependencies to come from other MacPorts
packages; the emacs-mac-app port depends on the libxml2 port, which
would be installed in /opt/local, so as far as I can tell this output
is correct.)

-Aaron