From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/lcdproc: override freetype-config path
Date: Sun, 11 Jun 2017 17:49:55 +0200 [thread overview]
Message-ID: <20170611174955.28f5994e@windsurf.home> (raw)
In-Reply-To: <20170611131317.16345-1-romain.naour@gmail.com>
Hello,
On Sun, 11 Jun 2017 15:13:16 +0200, Romain Naour wrote:
> freetype-config from the host system may be used when installed.
> Make sure that the one from HOST_DIR is used.
>
> checking if freetype support has been enabled... yes
> checking for freetype-config... /usr/bin/freetype-config
> checking for FreeType -- version >= 7.0.1... cross compiling; assuming OK... yes
>
> Fixes:
> http://autobuild.buildroot.net/results/c7c/c7c52cd56b985fd73434d5997e9a6ab3f7d7e71e
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/lcdproc/lcdproc.mk | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master, thanks. However, it's quite surprising to see this
change, only a week after you did commit
ce2e622dfe8a3f36bdf0c25b37a9f6ebbb23b6cc. What happened?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-11 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 13:13 [Buildroot] [PATCH 1/2] package/lcdproc: override freetype-config path Romain Naour
2017-06-11 13:13 ` [Buildroot] [PATCH 2/2] package lcdproc: override libpng-config path Romain Naour
2017-06-11 13:23 ` Thomas Petazzoni
2017-06-11 13:35 ` Romain Naour
2017-06-11 15:52 ` Thomas Petazzoni
2017-06-11 15:49 ` Thomas Petazzoni [this message]
2017-06-11 20:48 ` [Buildroot] [PATCH 1/2] package/lcdproc: override freetype-config path Romain Naour
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=20170611174955.28f5994e@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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