From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libgtk2: point to the proper cups-config
Date: Sat, 26 Mar 2016 21:35:22 +0100 [thread overview]
Message-ID: <20160326213522.4705ee0b@free-electrons.com> (raw)
In-Reply-To: <1459019854-13008-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Sat, 26 Mar 2016 16:17:34 -0300, Gustavo Zacarias wrote:
> Otherwise it can pick up the distro cups-config if it's present, leading
> to improper library usage/linkage. Fixes:
> http://autobuild.buildroot.net/results/bf4/bf493977817a750427aae82e71a5257187bd7344/
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/libgtk2/libgtk2.mk | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-26 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 19:17 [Buildroot] [PATCH] libgtk2: point to the proper cups-config Gustavo Zacarias
2016-03-26 20:35 ` Thomas Petazzoni [this message]
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=20160326213522.4705ee0b@free-electrons.com \
--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