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: Simon Leinen <simon.leinen@switch.ch>
Cc: 36758-done@debbugs.gnu.org
Subject: bug#36758: 27.0.50; Mac OS/Lucid/X11: crash with libharfbuzz
Date: Tue, 30 Jul 2019 09:03:24 +0900	[thread overview]
Message-ID: <wllfwg4cdv.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <aasgqygf54.fsf@switch.ch>

On Tue, 23 Jul 2019 02:20:23 +0900,
Simon Leinen wrote:
> 
> Simon Leinen writes:
> > So I guess all I have to do is make sure Emacs doesn't use the old
> > libfreetype in /opt/X11/lib, but rather the newer one in
> > /usr/local/lib (and hope that that one works in an X11 environment...)
> 
> I finally managed to get the Emacs Makefiles put
> -L/usr/local/opt/freetype/lib in front of -L/opt/X11/lib, and rebuilt my
> Emacs binaries.  They now no longer crash when I open the message with
> the Arabic font in GNUS.  Hooray!
> 
> So the problem was a typical "DLL hell" issue that I brought upon myself
> by selecting an unusual combination of libraries.  I don't think there's
> much for the Emacs developers to improve in this situation.  Therefore I
> think this bug can safely be closed.

Thanks for confirming it.  Closing the bug.

For future reference, FreeType 2.7.0 bundled with XQuartz 2.7.11
crashes if used with HarfBuzz 2.5.3, but FreeType 2.10.1 doesn't.

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





      reply	other threads:[~2019-07-30  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  7:09 bug#36758: 27.0.50; Mac OS/Lucid/X11: crash with libharfbuzz Simon Leinen
2019-07-22  8:15 ` YAMAMOTO Mitsuharu
2019-07-22  8:42   ` Simon Leinen
2019-07-22  9:58     ` YAMAMOTO Mitsuharu
2019-07-22 10:52       ` Simon Leinen
2019-07-22 11:13         ` YAMAMOTO Mitsuharu
2019-07-22 11:19           ` Simon Leinen
2019-07-22 17:20             ` Simon Leinen
2019-07-30  0:03               ` YAMAMOTO Mitsuharu [this message]

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=wllfwg4cdv.wl-mituharu@math.s.chiba-u.ac.jp \
    --to=mituharu@math.s.chiba-u.ac.jp \
    --cc=36758-done@debbugs.gnu.org \
    --cc=simon.leinen@switch.ch \
    /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).