From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33771@debbugs.gnu.org, far.nasiri.m@gmail.com,
Mike Kupfer <mkupfer@alum.berkeley.edu>
Subject: bug#33771: 27.0.50; Error building Harfbuzz branch on Debian testing
Date: Tue, 18 Dec 2018 16:06:48 +0100 [thread overview]
Message-ID: <CAArVCkTPecxL5=k96414eZGqdrHRR8cBLyV+R_U+y=qEZW6r3Q@mail.gmail.com> (raw)
In-Reply-To: <83woo6dgh1.fsf@gnu.org>
Am Di., 18. Dez. 2018 um 16:04 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Mon, 17 Dec 2018 21:34:52 +0100
> > Cc: Mike Kupfer <mkupfer@alum.berkeley.edu>, 33771@debbugs.gnu.org,
> > far.nasiri.m@gmail.com
> >
> > > > CC ftfont.o
> > > > ftfont.c:2819:1: warning: ‘ftfont_shape_by_hb’ defined but not used
> > > > [-Wunused-function]
> > > > ftfont_shape_by_hb (Lisp_Object lgstring, FT_Face ft_face, hb_font_t *hb_font,
> > > > ^~~~~~~~~~~~~~~~~~
> > > > ftfont.c:482:1: warning: ‘ftfont_get_hb_font’ defined but not used
> > > > [-Wunused-function]
> > > > ftfont_get_hb_font (struct ftfont_info *ftfont_info)
> > > > ^~~~~~~~~~~~~~~~~~
> > >
> > > I tried to fix that, please test.
> >
> > Sure, now I get two different warnings:
> >
> > CC ftfont.o
> > ftfont.c:2804:1: warning: ‘get_hb_unicode_funcs’ defined but not used
> > [-Wunused-function]
> > get_hb_unicode_funcs (void)
> > ^~~~~~~~~~~~~~~~~~~~
> > ftfont.c:482:1: warning: ‘ftfont_get_hb_font’ defined but not used
> > [-Wunused-function]
> > ftfont_get_hb_font (struct ftfont_info *ftfont_info)
> > ^~~~~~~~~~~~~~~~~~
>
> Any improvement now?
We're down to 1 warning:
CC ftfont.o
ftfont.c:482:1: warning: ‘ftfont_get_hb_font’ defined but not used
[-Wunused-function]
ftfont_get_hb_font (struct ftfont_info *ftfont_info)
^~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2018-12-18 15:06 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
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 [this message]
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='CAArVCkTPecxL5=k96414eZGqdrHRR8cBLyV+R_U+y=qEZW6r3Q@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=33771@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=far.nasiri.m@gmail.com \
--cc=mkupfer@alum.berkeley.edu \
/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).