public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/libglib2: restore use of system printf
Date: Fri, 08 May 2020 09:15:58 +0200	[thread overview]
Message-ID: <87h7wqucb5.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200421225131.5411a02a@windsurf.home> (Thomas Petazzoni's message of "Tue, 21 Apr 2020 22:51:31 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > On Wed, 11 Mar 2020 11:22:56 +0000
 > John Keeping <john@metanate.com> wrote:

 >> Prior to commit 4102db0f7a ("package/libglib2: bump to version 2.60.3")
 >> which converted libglib2 to meson, Buildroot used to set a range of
 >> autoconf options to bypass tests that require running binaries.
 >> 
 >> The meson version of libglib2's build system has many fewer of these
 >> checks, but there are still some and these can be fed the "correct"
 >> answer by adding properties to cross-compilation.conf.
 >> 
 >> Add the necessary properties to indicate that we have C99 compliant
 >> print functions to avoid pulling in the gnulib fallback.
 >> 
 >> Signed-off-by: John Keeping <john@metanate.com>
 >> Reviewed-by: Peter Seiderer <ps.report@gmx.net>
 >> ---
 >> v2:
 >> - Add Peter's reviewed-by - thanks!
 >> ---
 >> package/libglib2/libglib2.mk | 5 +++++
 >> 1 file changed, 5 insertions(+)

 > Applied to master, thanks.

Committed to 2020.02.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2020-05-08  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 11:22 [Buildroot] [PATCH v2 1/2] package/pkg-meson.mk: add FOO_MESON_EXTRA_PROPERTIES John Keeping
2020-03-11 11:22 ` [Buildroot] [PATCH v2 2/2] package/libglib2: restore use of system printf John Keeping
2020-04-21 20:51   ` Thomas Petazzoni
2020-05-08  7:15     ` Peter Korsgaard [this message]
2020-03-12 20:38 ` [Buildroot] [PATCH v2 1/2] package/pkg-meson.mk: add FOO_MESON_EXTRA_PROPERTIES Adam Duskett
2020-03-22 21:40 ` Yann E. MORIN

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=87h7wqucb5.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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