From: Nathaniel Bass <nw3455@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 38031@debbugs.gnu.org, Alan Third <alan@idiocy.org>,
Michael Dixon <dixius99@gmail.com>
Subject: bug#38031: 26.3; Trying to invoke the macOS File Open window causes Emacs to crash on macOS Catalina
Date: Thu, 7 Nov 2019 21:06:43 -0800 [thread overview]
Message-ID: <CACpZOn9s=KC0S1evus2JW-0M8JBWpNMgePOiG-Tx2kG-Fy8JSw@mail.gmail.com> (raw)
In-Reply-To: <871rujyzf3.fsf@marxist.se>
[-- Attachment #1: Type: text/plain, Size: 2835 bytes --]
I tried and before I got to testing the patch I ran into an issue building
Emacs on macOS 10.15 (aka Catalina).
When I run make I get the following error:
xml.c:26:10: fatal error: 'libxml/tree.h' file not found
#include <libxml/tree.h>
^~~~~~~~~~~~~~~
1 error generated.
make[1]: *** [xml.o] Error 1
make: *** [src] Error 2
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C lib all
make[1]: Nothing to be done for `all'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C lib-src all
make[1]: Nothing to be done for `all'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C src
VCSWITNESS='$(srcdir)/../.git/logs/HEAD' all
CC xml.o
xml.c:26:10: fatal error: 'libxml/tree.h' file not found
#include <libxml/tree.h>
^~~~~~~~~~~~~~~
1 error generated.
make[1]: *** [xml.o] Error 1
make: *** [src] Error 2
Mac OS X 10.14 has stopped placing the include libraries in their usual
location, /usr/include, keeping them only inside the XCode directory.
The work around was to run a pkg installer included in the XCode
directory.[1] I can no longer find that file or anything similar in macOS
10.15.
Any tips are appreciated. I will try to build and test the patch again this
weekend. There was something in the article I referenced about linking the
path where the libraries are to /usr/include but it wasn't recommended
because it overrides the default behaviour expected by Mac OS and requires
you to disable SIP (System Integrity Protection). I am open to trying
anything.
[1]
https://silvae86.github.io/sysadmin/mac/osx/mojave/beta/libxml2/2018/07/05/fixing-missing-headers-for-homebrew-in-mac-osx-mojave/
Other links about this issue:
https://lists.gnu.org/archive/html/emacs-devel/2015-11/msg01918.html
https://emacs.stackexchange.com/questions/34238/installing-emacs-from-source-make-fatal-error-libxml-tree-h-file-not-found
On Thu, Nov 7, 2019, 4:40 PM Stefan Kangas <stefan@marxist.se> wrote:
>
> Alan Third <alan@idiocy.org> writes:
>
> > On Sun, Nov 03, 2019 at 04:02:39PM -0500, Michael Dixon wrote:
> >> Thanks Alan. I might be a little over my head here, as I’m not sure
> >> how to apply a patch. I presume I would have to build from source...
> >
> > Yes, you would. It’s not very hard if you’ve got git installed. I can
> > talk you through it. Alternatively we can try to find someone else
> > running Catalina, there should be a few Emacs devs/users who’ve
> > upgraded around here somewhere.
>
> I'm still on 10.13 so I unfortunately can't help with this. But since
> this is a crash in very basic functionality, perhaps we should
> actively reach out to try to see if anyone can help with this in time
> to fix it before the pretest of Emacs 27.1.
>
> Best regards,
> Stefan Kangas
>
>
[-- Attachment #2: Type: text/html, Size: 3653 bytes --]
next prev parent reply other threads:[~2019-11-08 5:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 10:19 bug#38031: 26.3; Trying to invoke the macOS File Open window causes Emacs to crash on macOS Catalina Michael Dixon
2019-11-03 20:39 ` Alan Third
2019-11-03 21:02 ` Michael Dixon
2019-11-04 20:06 ` Alan Third
2019-11-08 0:39 ` Stefan Kangas
2019-11-08 5:06 ` Nathaniel Bass [this message]
2019-11-08 19:47 ` Alan Third
2019-11-08 21:33 ` Michael Dixon
2019-11-08 23:08 ` Alan Third
2019-11-08 23:17 ` Michael Dixon
2020-01-14 21:39 ` Alan Third
2020-01-15 3:00 ` Michael Dixon
2020-01-15 19:00 ` Alan Third
2020-01-15 21:48 ` Michael Dixon
2020-01-17 18:53 ` Alan Third
2020-01-17 23:49 ` Michael Dixon
2020-01-18 15:22 ` Alan Third
2020-01-18 16:39 ` Michael Dixon
2020-01-18 20:50 ` Alan Third
2020-01-24 10:00 ` Alan Third
2019-11-08 7:02 ` Andrii Kolomoiets
2019-12-05 11:20 ` Michael Dixon
2019-12-06 1:57 ` Michael Dixon
2019-12-19 7:37 ` bug#38031: Same error Lars Hovdan Molden via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CACpZOn9s=KC0S1evus2JW-0M8JBWpNMgePOiG-Tx2kG-Fy8JSw@mail.gmail.com' \
--to=nw3455@gmail.com \
--cc=38031@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=dixius99@gmail.com \
--cc=stefan@marxist.se \
/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).