From: Kenichi Handa <handa@m17n.org>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: undefined reference to ftfont_variation_glyphs
Date: Mon, 30 Mar 2009 14:41:47 +0900 [thread overview]
Message-ID: <E1LoAFn-0007uX-KK@etlken> (raw)
In-Reply-To: <873acy3n9m.fsf@kassiopeya.MSHEIMNETZ> (message from Sebastian Rose on Fri, 27 Mar 2009 13:27:21 +0100)
Sorry for the late response on this matter.
In article <873acy3n9m.fsf@kassiopeya.MSHEIMNETZ>, Sebastian Rose <sebastian_rose@gmx.de> writes:
> Since a few days I cannot build CVS emacs 23 on debian.
> $ gcc --version
> gcc (Debian 4.3.3-3) 4.3.3
> ftfont.o:(.data+0x68): undefined reference to `ftfont_variation_glyphs'
[...]
> While declaration (line 384) and usage (line 431) of the function
> `ftfont_variation_glyphs()' are surounded solely by:
> #ifdef HAVE_OTF_GET_VARIATION_GLYPHS
> /* FUNCTION DECLARATION HERE */
> #endif /* HAVE_OTF_GET_VARIATION_GLYPHS */
Yes, it's a bug, and thank you for the patch. But, actually
ftfont_variation_glyphs is usable even without
HAVE_M17N_FLT. So, the right fix is to define it without
checking HAVE_M17N_FLT.
Chong Yidong <cyd@stupidchicken.com> writes:
> I've checked in your patch (with a slight correction). Thanks.
I've just installed another fix.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-03-30 5:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 12:27 undefined reference to ftfont_variation_glyphs Sebastian Rose
2009-03-27 17:19 ` Sebastian Rose
2009-03-27 19:35 ` Stefan Monnier
2009-03-27 21:39 ` Sebastian Rose
2009-03-28 4:19 ` Stefan Monnier
2009-03-28 16:43 ` Sebastian Rose
2009-03-29 17:15 ` Chong Yidong
2009-03-29 17:54 ` Sebastian Rose
2009-03-28 3:34 ` Chong Yidong
2009-03-28 16:37 ` Sebastian Rose
2009-03-28 19:02 ` Sebastian Rose
2009-03-30 5:41 ` Kenichi Handa [this message]
2009-03-30 11:26 ` Sebastian Rose
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1LoAFn-0007uX-KK@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=sebastian_rose@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.