unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel Mailinglist <emacs-devel@gnu.org>
Subject: Re: undefined reference to ftfont_variation_glyphs
Date: Sat, 28 Mar 2009 17:43:36 +0100	[thread overview]
Message-ID: <87bprl8uo7.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <jwvbprmcma8.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 28 Mar 2009 00:19:33 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> @@ -422,11 +429,15 @@
>>      NULL,
>>  #endif	/* not (HAVE_M17N_FLT && HAVE_LIBOTF) */
>>      NULL,			/* check */
>> +#ifdef HAVE_LIBOTF
>> +#ifdef HAVE_M17N_FLT
>>  #ifdef HAVE_OTF_GET_VARIATION_GLYPHS
>>      ftfont_variation_glyphs
>>  #else
>>      NULL
>>  #endif
>> +#endif
>> +#endif
>>    };
>  
> Makes me wonder: how come HAVE_OTF_GET_VARIATION_GLYPHS is defined for
> you if ftfont_variation_glyphs isn't?
>
>
>         Stefan

I don't know anything about the emacs code. I think HAVE_LIBOTF is
defined, since ./configure finds libotf.

If HAVE_OTF_GET_VARIATION_GLYPHS is defined in this case, the culprit
might be HAVE_M17N_FLT.

No matter which one is defined or not, it seems wrong to enclose a
functions declaration, usage, and definition in different sets of
include guards.


Regards,

   Sebastian




  reply	other threads:[~2009-03-28 16:43 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 [this message]
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
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

  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=87bprl8uo7.fsf@kassiopeya.MSHEIMNETZ \
    --to=sebastian_rose@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).