From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libglib2: disable tests and update configure options
Date: Tue, 27 Oct 2015 07:33:55 +0100 [thread overview]
Message-ID: <20151027073355.62029b0e@free-electrons.com> (raw)
In-Reply-To: <1445380855-31482-1-git-send-email-gustavo.zacarias@free-electrons.com>
Gustavo,
On Tue, 20 Oct 2015 19:40:55 -0300, gustavo.zacarias at free-electrons.com
wrote:
> From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
>
> Sometimes if host-python is around it doesn't work too well with the
> distro python (Gentoo, FC20 at least) leading to build failures.
>
> This failure is very hard to trigger, it's normally easier to do so by
> enabling top-level parallel builds.
>
> Fixes:
> http://autobuild.buildroot.net/results/0f8/0f881e322b7f9d244b8dd2440ba0afd3a8418027/
>
> While at it update the configure options to avoid any host
> libraries/tools from leaking in, new naming conventions and options.
> And remove dead code dealing with the nothreaded variant.
>
> Signed-off-by: Gustavo Zacarias <gustavozacarias@free-electrons.com>
> ---
> package/libglib2/0002-disable-tests.patch | 43 +++++++++++++++++++++++++++++++
> package/libglib2/libglib2.mk | 12 ++++-----
> 2 files changed, 48 insertions(+), 7 deletions(-)
> create mode 100644 package/libglib2/0002-disable-tests.patch
Applied, thanks. However, I would have preferred the patch to be in a
form that can potentially be upstreamed (i.e addition of a ./configure
option to disable tests), and the said patch to actually be submitted
upstream.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-10-27 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:40 [Buildroot] [PATCH] libglib2: disable tests and update configure options gustavo.zacarias at free-electrons.com
2015-10-27 6:33 ` 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=20151027073355.62029b0e@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 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.