All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: Bump to version 2.56.3
Date: Sun, 30 Dec 2018 21:27:45 +0100	[thread overview]
Message-ID: <20181230212745.196c01c3@windsurf> (raw)
In-Reply-To: <20181230193432.GA10930@x230>

Hello,

On Sun, 30 Dec 2018 20:34:33 +0100, Petr Vorel wrote:

> >  ...gobject-fix-compilation-with-gcc-4.7.patch | 50 ------------------
> >  ...compilation-without-F_-S-G-ETPIPE_SZ.patch | 52 -------------------
> >  package/libglib2/libglib2.hash                |  4 +-
> >  package/libglib2/libglib2.mk                  |  2 +-
> >  4 files changed, 3 insertions(+), 105 deletions(-)
> >  delete mode 100644 package/libglib2/0003-gobject-fix-compilation-with-gcc-4.7.patch
> >  delete mode 100644 package/libglib2/0005-gio-fix-compilation-without-F_-S-G-ETPIPE_SZ.patch  
> 
> Ping, please.

I tried to merge a similar bump a few weeks ago, and it caused massive
build failures, so I had to revert. In the mean time, I applied the
pkg-config bump, which also caused lots of issues, which have
apparently now been all addressed, so it will be a good time to merge a
libglib2 bump.

However, was this tested with a large number of libglib2 reverse
dependencies ?

See
https://git.buildroot.org/buildroot/commit/package/libglib2?id=2694222c3d3663d9fcc55e6cf44a45b74b43793f
for details.

Did you try to build dbus-glib on the latest master, with the libglib2
bump included ?

I would be more convinced with a commit log that provides a defconfig
with lots of libglib2 reverse dependencies enabled, with the statement
that this defconfig continues to build fine after the libglib2 bump.

Thanks!

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

  reply	other threads:[~2018-12-30 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 17:38 [Buildroot] [PATCH 1/1] libglib2: Bump to version 2.56.3 Petr Vorel
2018-12-30 19:34 ` Petr Vorel
2018-12-30 20:27   ` Thomas Petazzoni [this message]
2018-12-30 20:34     ` Petr Vorel
2018-12-30 21:02       ` Thomas Petazzoni
2018-12-30 21:46 ` Thomas Petazzoni

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=20181230212745.196c01c3@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 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.