From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12901] GStreamer doesn't build on 2020-05 rc1 with GObject introspection enabled (wrong path for g-ir-scanner)
Date: Sat, 16 May 2020 09:40:34 +0000 [thread overview]
Message-ID: <bug-12901-163-cUePAQ3GWl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12901-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12901
--- Comment #2 from Fabrice Fontaine <fontaine.fabrice@gmail.com> ---
Hi,
Thanks for the bug report, this is a known issue, all meson packages fail to
build with gobject-introspection.
You can find a patch fixing this issue here:
https://patchwork.ozlabs.org/project/buildroot/patch/20200502060435.23004-1-james.hilliard1 at gmail.com/.
However, this patch has not been merged and probably won't be. James waits for
the next meson release before sending an updated version of this patch (see
https://patchwork.ozlabs.org/project/buildroot/patch/20200315172459.881615-2-aduskett at gmail.com/)
Best Regards,
Fabrice
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-16 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 5:37 [Buildroot] [Bug 12901] New: GObject introspection doesn't build on 2020-05 rc1 (wrong path for g-ir-scanner) bugzilla at busybox.net
2020-05-16 6:21 ` [Buildroot] [Bug 12901] GStreamer doesn't build " bugzilla at busybox.net
2020-05-16 6:24 ` bugzilla at busybox.net
2020-05-16 6:24 ` [Buildroot] [Bug 12901] GStreamer doesn't build on 2020-05 rc1 with GObject introspection enabled " bugzilla at busybox.net
2020-05-16 9:40 ` bugzilla at busybox.net [this message]
2020-05-16 12:04 ` bugzilla at busybox.net
2020-05-17 7:28 ` bugzilla at busybox.net
2020-05-18 11:26 ` bugzilla at busybox.net
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=bug-12901-163-cUePAQ3GWl@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.