From: Zach Pearson <zach@zjp.codes>
To: mituharu@math.s.chiba-u.ac.jp
Cc: emacs-devel@gnu.org
Subject: Re: Compilation failure on macOS 10.15 Catalina
Date: Wed, 25 Sep 2019 16:55:11 -0500 [thread overview]
Message-ID: <5553DB40-43BF-4980-BAB7-59D4668C42E8@zjp.codes> (raw)
In-Reply-To: <6c6acaf1143135c5a99ea86a3f61b394.squirrel@weber.math.s.chiba-u.ac.jp>
Sorry for the double reply, I forgot to cc the mailing list. Whoops.
To the first:
-I/usr/local/Cellar/libxml2/2.9.9_2/include/libxml2 -L/usr/local/Cellar/libxml2/2.9.9_2/lib -lxml2
And the second:
/usr/local/opt/libxml2/lib/pkgconfig
> On 25 Sep 2019, at 15:29, mituharu@math.s.chiba-u.ac.jp wrote:
>
>> I think that Apple has changed the way the Xcode command line tools
>> arrange headers on the system e.g. they are no longer put into
>> /usr/include but exist in
>>
>> /Library/Developer/CommandLineTools/usr/include/
>>
>> Because of this Emacs cannot find libxml/tree.h during the compilation
>> process.
>
> The current configure script is supposed to handle this situation.
> I suspect you have bogus libxml-2.0.pc referring to /usr/include.
> What is the output of the following commands?
>
> $ pkg-config --cflags --libs "libxml-2.0 > 2.6.17"
> $ pkg-config --variable pcfiledir "libxml-2.0 > 2.6.17"
>
> See also https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32927
>
> YAMAMOTO Mitsuharu
> mituharu@math.s.chiba-u.ac.jp
>
>
>
next prev parent reply other threads:[~2019-09-25 21:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 11:28 Returning argument string (regexp-quote) Mattias Engdegård
2019-09-24 11:49 ` Andreas Schwab
2019-09-24 16:20 ` Eli Zaretskii
2019-09-24 17:44 ` Mattias Engdegård
2019-09-24 18:24 ` Paul Eggert
2019-09-24 19:47 ` Eli Zaretskii
2019-09-25 13:41 ` Mattias Engdegård
2019-09-25 15:08 ` Eli Zaretskii
2019-09-25 19:55 ` Compilation failure on macOS 10.15 Catalina Zach Pearson
2019-09-25 20:29 ` mituharu
2019-09-25 21:55 ` Zach Pearson [this message]
2019-09-25 22:47 ` mituharu
2019-09-25 23:07 ` Zach Pearson
2019-09-25 23:39 ` mituharu
2019-09-27 23:22 ` chad
2019-10-02 3:59 ` Zach Pearson
2019-10-02 4:04 ` YAMAMOTO Mitsuharu
2019-10-02 4:34 ` Zach Pearson
2019-10-02 4:42 ` YAMAMOTO Mitsuharu
2019-10-02 4:43 ` Zach Pearson
2019-10-02 5:00 ` YAMAMOTO Mitsuharu
2019-10-02 5:07 ` Zach Pearson
2019-10-02 7:43 ` Zach Pearson
2019-10-02 15:15 ` Xu Xin
2019-09-26 8:34 ` Robert Pluim
2019-09-26 16:05 ` Zach Pearson
2019-09-26 21:00 ` mituharu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5553DB40-43BF-4980-BAB7-59D4668C42E8@zjp.codes \
--to=zach@zjp.codes \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).