From: Mike Kupfer <mkupfer@alum.berkeley.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philipp <p.stephani2@gmail.com>,
33771@debbugs.gnu.org, far.nasiri.m@gmail.com
Subject: bug#33771: 27.0.50; Error building Harfbuzz branch on Debian testing
Date: Sun, 16 Dec 2018 21:18:04 -0800 [thread overview]
Message-ID: <28241.1545023884@alto> (raw)
In-Reply-To: Your message of "Sun\, 16 Dec 2018 21\:52\:34 +0200." <83r2ehdzb1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]
Eli Zaretskii wrote:
> Does the below fix the problem?
It helps, thanks. I needed to make a similar change in a few other
places, at least for building on Solaris. I've attached the patch I
ended up with.
I still can't get a clean build, because of
Checking /export/home/kupfer/src/emacs-git/lisp/leim/quail/japanese.el ...
Fatal error 11: Segmentation Fault
Backtrace:
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'emacs_backtrace+0x43 [0x5b63f3]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'terminate_due_to_signal+0x8b [0x59c40b]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'0x1b4cfe [0x5b4cfe]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'deliver_thread_signal.constprop.13+0x2a [0x5b4eea]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'handle_sigsegv+0x1f [0x5b4f4f]
/lib/amd64/libc.so.1'__sighndlr+0x6 [0x7fffbe44ebe6]
/lib/amd64/libc.so.1'call_user_handler+0x2f1 [0x7fffbe4406b1]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'decode_char+0x3db [0x53804b]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'decode_coding_iso_2022+0x141e [0x544bde]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'decode_coding+0x18f [0x54976f]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'decode_coding_gap+0x15f [0x550f9f]
/export/home/kupfer/src/emacs-git/src/bootstrap-emacs'Finsert_file_contents+0x11fb [0x5cf5eb]
...
I got the same failure building master, so it's not related to HarfBuzz.
I'll follow up about this second failure when I get some time; maybe
next week.
cheers,
mike
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch: HarfBuzz but no libotf --]
[-- Type: text/x-diff, Size: 2755 bytes --]
diff --git a/src/ftcrfont.c b/src/ftcrfont.c
index 6d74d937a7..ae5b0a92ee 100644
--- a/src/ftcrfont.c
+++ b/src/ftcrfont.c
@@ -302,7 +302,7 @@ struct font_driver const ftcrfont_driver =
#ifdef HAVE_LIBOTF
.otf_capability = ftfont_otf_capability,
#endif
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
.shape = ftfont_shape,
#endif
#ifdef HAVE_OTF_GET_VARIATION_GLYPHS
diff --git a/src/ftfont.c b/src/ftfont.c
index bc98896393..bbdc936ffd 100644
--- a/src/ftfont.c
+++ b/src/ftfont.c
@@ -2931,7 +2931,7 @@ ftfont_shape_by_hb (Lisp_Object lgstring, FT_Face ft_face, hb_font_t *hb_font,
#endif /* HAVE_HARFBUZZ */
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
Lisp_Object
ftfont_shape (Lisp_Object lgstring)
@@ -2956,7 +2956,7 @@ ftfont_shape (Lisp_Object lgstring)
}
}
-#endif /* defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ */
+#endif /* HAVE_LIBOTF && (HAVE_M17N_FLT || defined HAVE_HARFBUZZ) */
static const char *const ftfont_booleans [] = {
":antialias",
@@ -3037,7 +3037,7 @@ static struct font_driver const ftfont_driver =
#ifdef HAVE_LIBOTF
.otf_capability = ftfont_otf_capability,
#endif
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
.shape = ftfont_shape,
#endif
#ifdef HAVE_OTF_GET_VARIATION_GLYPHS
diff --git a/src/ftxfont.c b/src/ftxfont.c
index 4d4ff6ee0c..a30b07636e 100644
--- a/src/ftxfont.c
+++ b/src/ftxfont.c
@@ -359,7 +359,7 @@ struct font_driver const ftxfont_driver =
.otf_capability = ftfont_otf_capability,
#endif
.end_for_frame = ftxfont_end_for_frame,
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
.shape = ftfont_shape,
#endif
#ifdef HAVE_OTF_GET_VARIATION_GLYPHS
diff --git a/src/xftfont.c b/src/xftfont.c
index e0bd243467..5111936f3e 100644
--- a/src/xftfont.c
+++ b/src/xftfont.c
@@ -672,7 +672,7 @@ xftfont_draw (struct glyph_string *s, int from, int to, int x, int y,
return len;
}
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
static Lisp_Object
xftfont_shape (Lisp_Object lgstring)
{
@@ -784,7 +784,7 @@ struct font_driver const xftfont_driver =
.otf_capability = ftfont_otf_capability,
#endif
.end_for_frame = xftfont_end_for_frame,
-#if defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ
+#if defined HAVE_LIBOTF && (defined HAVE_M17N_FLT || defined HAVE_HARFBUZZ)
.shape = xftfont_shape,
#endif
#ifdef HAVE_OTF_GET_VARIATION_GLYPHS
next prev parent reply other threads:[~2018-12-17 5:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 18:57 bug#33771: 27.0.50; Error building Harfbuzz branch on Debian testing Philipp
2018-12-16 19:52 ` Eli Zaretskii
2018-12-17 5:18 ` Mike Kupfer [this message]
2018-12-17 17:11 ` Eli Zaretskii
2018-12-17 17:20 ` Philipp Stephani
2018-12-17 17:46 ` Eli Zaretskii
2018-12-17 20:34 ` Philipp Stephani
2018-12-18 15:03 ` Eli Zaretskii
2018-12-18 15:06 ` Philipp Stephani
2018-12-18 18:46 ` Eli Zaretskii
2018-12-18 19:22 ` Philipp Stephani
2018-12-17 17:24 ` Philipp Stephani
2018-12-16 19:58 ` Mike Kupfer
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=28241.1545023884@alto \
--to=mkupfer@alum.berkeley.edu \
--cc=33771@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=far.nasiri.m@gmail.com \
--cc=p.stephani2@gmail.com \
/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).