Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH, next 1/1] package/libglib2: bump to version 2.62.2
Date: Tue, 12 Nov 2019 21:53:41 +0100	[thread overview]
Message-ID: <20191112215341.28f7b1aa@windsurf> (raw)
In-Reply-To: <20191111210251.2216431-1-aduskett@gmail.com>

Hello Adam,

On Mon, 11 Nov 2019 13:02:51 -0800
aduskett at gmail.com wrote:

> diff --git a/package/libglib2/0002-add-option-to-build-tests.patch b/package/libglib2/0002-add-option-to-build-tests.patch
> index 5caaaff6b2..5f0d638dbf 100644
> --- a/package/libglib2/0002-add-option-to-build-tests.patch
> +++ b/package/libglib2/0002-add-option-to-build-tests.patch

This patch is no longer adding an option to build tests, so I'm
surprised that the title/commit description hasn't changed.

> + # Don?t build the tests unless we can run them (either natively, in an exe wrapper, or by installing them for later use)
> +-build_tests = not meson.is_cross_build() or (meson.is_cross_build() and meson.has_exe_wrapper()) or installed_tests_enabled
> ++build_tests = installed_tests_enabled

Why do we need to change this ? Is meson.has_exe_wrapper() true in our case ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-12 20:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11 21:02 [Buildroot] [PATCH, next 1/1] package/libglib2: bump to version 2.62.2 aduskett at gmail.com
2019-11-12 20:53 ` Thomas Petazzoni [this message]
2019-11-13 19:19   ` Adam Duskett
2019-11-13 19:45     ` Thomas Petazzoni
2019-11-14 16:12       ` Adam Duskett
2019-11-14 20:14         ` Peter Seiderer
2019-11-14 22:52           ` Adam Duskett

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=20191112215341.28f7b1aa@windsurf \
    --to=thomas.petazzoni@bootlin.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