All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: fedora.dm0@gmail.com
Subject: Re: [BUG][PATCH] configure.ac: Respect the configured freetype-config
Date: Fri, 7 Jun 2013 22:20:02 +0400	[thread overview]
Message-ID: <20130607222002.6d37ec61@opensuse.site> (raw)
In-Reply-To: <CAEvUa7ki25JDVF_QQnNsVDwWvkpzvd0xBZpTF1EzVqoLvaFx0w@mail.gmail.com>

В Fri, 7 Jun 2013 14:04:59 -0400
David Michael <fedora.dm0@gmail.com> пишет:

> Hi,
> 
> It seems that the configure script detects freetype-config in the
> usual manner, but when this command is needed, it will only call a
> hard-coded freetype-config.
> 

But FREETYPE cannot be anything than freetype-config, can it? Do you
actually have situation when AC_CHECK_PROGS([FREETYPE],
[freetype-config]) succeeds but call to freetype-config fails?

> Can something like this fix be applied to call the configured program?
> 
> Thanks.
> 
> David
> 
> 
> === modified file 'configure.ac'
> --- configure.ac    2013-06-07 14:02:16 +0000
> +++ configure.ac    2013-06-07 17:45:34 +0000
> @@ -952,8 +952,8 @@
> 
>  if test x"$grub_mkfont_excuse" = x ; then
>    # Check for freetype libraries.
> -  freetype_cflags=`freetype-config --cflags`
> -  freetype_libs=`freetype-config --libs`
> +  freetype_cflags=`$FREETYPE --cflags`
> +  freetype_libs=`$FREETYPE --libs`
>    SAVED_CPPFLAGS="$CPPFLAGS"
>    CPPFLAGS="$CPPFLAGS $freetype_cflags"
>    AC_CHECK_HEADERS([ft2build.h], [],
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2013-06-07 18:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-07 18:04 [BUG][PATCH] configure.ac: Respect the configured freetype-config David Michael
2013-06-07 18:20 ` Andrey Borzenkov [this message]
2013-06-07 18:35   ` David Michael
2013-06-08  4:00     ` Andrey Borzenkov
2013-06-09 21:10       ` Paul Menzel
2013-06-10 21:05       ` David Michael
2013-06-11 14:31         ` David Michael
2013-06-11 14:48           ` Andrey Borzenkov
2013-06-11 15:23             ` David Michael
2013-06-11 15:41               ` Andrey Borzenkov
2013-06-11 17:31                 ` David Michael
2013-06-15 19:08                   ` Vladimir 'φ-coder/phcoder' Serbinenko

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=20130607222002.6d37ec61@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=fedora.dm0@gmail.com \
    --cc=grub-devel@gnu.org \
    /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. 
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.