unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Glenn Morris <rgm@gnu.org>
Cc: Philipp <p.stephani2@gmail.com>, 32927@debbugs.gnu.org
Subject: bug#32927: 27.0.50; libxml not found when building on macOS Mojave
Date: Thu, 04 Oct 2018 14:24:04 +0900	[thread overview]
Message-ID: <wlsh1me13f.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <6oo9cask2c.fsf@fencepost.gnu.org>

On Thu, 04 Oct 2018 08:10:35 +0900,
Glenn Morris wrote:
> 
> 
> Is this the perennial "xcode-select --install" issue again?
> 
> Bug#18779, 22552, 24068, 27526#74, 29931, ...
> https://lists.gnu.org/r/emacs-devel/2015-11/msg01926.html

I've received a similar report for the Mac port, and the situation was
a bit different.  Unlike the previous versions, the Command Line Tools
package for Xcode 10 no longer installs the header files into
/usr/include on macOS 10.14 (*).

*: https://developer.apple.com/documentation/xcode_release_notes/xcode_10_release_notes

The culprit for the above case was the bogus libxml-2.0.pc file that
refers to nonexistent /usr/include.  Philipp, could you try

  $ pkg-config --cflags --libs "libxml-2.0 > 2.6.17

to see if it refers to /usr/include ?  If so, locate the erroneous
config file by the following command:

  $ pkg-config --variable pcfiledir "libxml-2.0 > 2.6.17"

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp





  reply	other threads:[~2018-10-04  5:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 21:19 bug#32927: 27.0.50; libxml not found when building on macOS Mojave Philipp
2018-10-03 23:10 ` Glenn Morris
2018-10-04  5:24   ` YAMAMOTO Mitsuharu [this message]
2018-10-04 21:22     ` Philipp Stephani
2018-10-05  0:34       ` YAMAMOTO Mitsuharu
2018-10-15 14:52         ` Xu Xin

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=wlsh1me13f.wl-mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=32927@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=rgm@gnu.org \
    /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).