Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: bump to version 2.58.1
Date: Mon, 3 Dec 2018 09:11:24 +0100	[thread overview]
Message-ID: <20181203081124.GD2649@scaer> (raw)
In-Reply-To: <CAPi7W802dzjZhNuw-07vtBvuoFRGnhc+qhZf=ZhH3Ra11GrHuw@mail.gmail.com>

Fabrice, All,

On 2018-12-03 08:23 +0100, Fabrice Fontaine spake thusly:
> Le dim. 2 d?c. 2018 ? 18:23, Yann E. MORIN <yann.morin.1998@free.fr> a ?crit :
> > On 2018-12-02 14:00 +0100, Thomas Petazzoni spake thusly:
> > > On Sun, 14 Oct 2018 09:58:52 +0200, Fabrice Fontaine wrote:
> > As you can see on the autobuilders, thius breaks all glib-using packages:
[--SNIP--]
> > So, the solutions I have for now are:
> >
> >  1- fix each package and pass them GLIB_GENMARSHAL=$(STAGING_DIR)/bin/glib-genmarshal
> >     (similarly for the two other tools)
> >
> >  2- teach pkgconf to replace even more variables. This is not very
> >     satisfying, and we won't be able to keep up in the long term. We
> >     hould at least teach pkgconf to look for that list in an environment
> >     variable, at least, to avoid tweaking the code over-and-over again.
[--SNIP--]
> Thanks a lot for investigating, I'm more in favor of (2) because most
> of the glib packages don't have any environment variables.
> However, it should be noted that a lot of glib packages (libsoup,
> gdk-pixpuf, atk, pango) have switched to meson in their latest
> upstream versions.
> Meson has a gnome module to find and call genmarshal, mkenums, etc ...
> and this module does not use the pkgconfig file to find the path of
> these binaries.

Well, dbus-glib is in maintenance-mode only, so it's not going to be
updated to meson I am afraid (or should I say, relieved?). So we still
have some fixing to do.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-12-03  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14  7:58 [Buildroot] [PATCH 1/1] libglib2: bump to version 2.58.1 Fabrice Fontaine
2018-12-02 13:00 ` Thomas Petazzoni
2018-12-02 17:23   ` Yann E. MORIN
2018-12-03  7:23     ` Fabrice Fontaine
2018-12-03  8:11       ` Yann E. MORIN [this message]
2018-12-03  7:38     ` Thomas Petazzoni
2018-12-03  8:06       ` 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=20181203081124.GD2649@scaer \
    --to=yann.morin.1998@free.fr \
    --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