Hi,
On Sat, Jun 8, 2013 at 12:00 AM, Andrey Borzenkov <arvidj...@gmail.com> wrote:
>> 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?
Sorry, I meant to say that it allows me to manually specify the path
to the proper freetype-config script. You are correct that configure
detects the system's native script by default, since it appears first
in $PATH.
I was referring to the behavior of overriding the AC_CHECK_PROGS
variable with configure arguments or environment variables. The patch
allows:
FREETYPE=/cross-stuff/bin/freetype-config ./configure ...
or
./configure FREETYPE=/cross-stuff/bin/freetype-config ...
which will then build the grub-mkfont utility with the proper system's
libraries.
Thanks.
David
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
