Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,
	 Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH 1/1] package/libglib2: drop unused 0001-meson.build-add-girdir-to-gio-2.0.pc-and-glib-2.0.pc.patch
Date: Mon, 29 Jun 2026 12:54:13 +0200	[thread overview]
Message-ID: <877bnhvcq2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260627120452.803450-1-fiona.klute@gmx.de> (Fiona Klute's message of "Sat, 27 Jun 2026 14:04:52 +0200")

>>>>> "Fiona" == Fiona Klute <fiona.klute@gmx.de> writes:

 > In 11aa1cfa5af9a77a0a9f726bd38f1b7db659c0bf the patch was accidentally
 > moved into a versioned directory with the wrong version (2.82.0
 > instead of 2.82.4) and thus not applied. However, there have been no
 > issues reported.

 > The patch description mentions being needed to fix build errors in
 > package/atk and package/libnice. It was originally added in
 > b094f88a4d501101bfba9b65491209e6a0fe0397, and amended for libnice in
 > 2c916b400bc608512db790d97df010ca666b6dd2. package/atk was removed in
 > 2c3ca7bea1de76163aeef432412eb14551ed0581, because atk has been merged
 > into at-spi2-core. Both at-spi2-core and libnice are Meson packages,
 > as was atk at the time of its removal.

 > Both current packages build with the following configuration (tested
 > using utils/test-pkg):

 > BR2_PACKAGE_PYTHON3=y
 > BR2_PACKAGE_GOBJECT_INTROSPECTION=y
 > BR2_PACKAGE_LIBNICE=y
 > BR2_PACKAGE_AT_SPI2_CORE=y

 > Evidently the patch is no longer needed, presumably because the
 > correct search path for GIR files is set by other means, and we can
 > remove it instead of fixing the version number of the patch directory.

 > Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
 > ---
 > I admit it is a bit unsatisfying that it's unclear exactly *what*
 > fixed that search path. Another bit of evidence I have is that when
 > working on that libglib2 2.82.x and gobject-introspection 1.82.0
 > version bump it was primarily for package/python-gobject, which also
 > uses Meson, so it probably was either that bump or a Meson bump at
 > some point before.

Committed, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-06-29 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 12:04 [Buildroot] [PATCH 1/1] package/libglib2: drop unused 0001-meson.build-add-girdir-to-gio-2.0.pc-and-glib-2.0.pc.patch Fiona Klute via buildroot
2026-06-29  7:42 ` Thomas Perale via buildroot
2026-06-29 15:11   ` Fiona Klute via buildroot
2026-06-29 10:54 ` Peter Korsgaard [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=877bnhvcq2.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.perale@mind.be \
    /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