grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: grub-devel@gnu.org
Subject: Re: [BUG][PATCH] configure.ac: Respect the configured freetype-config
Date: Sun, 09 Jun 2013 23:10:14 +0200	[thread overview]
Message-ID: <1370812214.5437.13.camel@mattotaupa> (raw)
In-Reply-To: <20130608080051.26e42526@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Am Samstag, den 08.06.2013, 08:00 +0400 schrieb Andrey Borzenkov:
> В Fri, 7 Jun 2013 14:35:10 -0400
> David Michael <fedora.dm0@gmail.com> пишет:

> > On Fri, Jun 7, 2013 at 2:20 PM, Andrey Borzenkov <arvidjaar@gmail.com> wrote:
> > > 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?
> > 
> > In my case, I noticed this issue while attempting to cross-compile
> > GRUB for another system. It needs to use the cross-compiled freetype
> > configuration, but the build system has its native freetype-config
> > installed as well.  Using a variable here allowed me to specify the
> > correct freetype-config as per the usual AC_CHECK_PROGS behavior.
> > 
> 
> I still do not understand it. AC_CHECK_PROG does not change behavior in
> case of cross-compilation, it simply finds first program in PATH.
> 
> Could you explain you setup in more details and show config.log both
> with and without your patch?

But later on

    freetype_cflags=`$FREETYPE --cflags`

is executed, which is going to get the CFLAGS from the build(?) system
(GRUB is built on) and not the target(?) system (GRUB is built for), so
the flags from the build system are going to be used (like x86 and not
ARM).

> > This isn't a big problem since I am able to build on the target system
> > as well, but it would be nice to have working out of the box.


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-06-09 21:10 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
2013-06-07 18:35   ` David Michael
2013-06-08  4:00     ` Andrey Borzenkov
2013-06-09 21:10       ` Paul Menzel [this message]
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=1370812214.5437.13.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --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 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 NNTP newsgroup(s).