From: Ross Burton <Ross.Burton@arm.com>
To: Lei Maohui <leimaohui@fujitsu.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] gstreamer1.0-dev: Fix install conflict when enable multilib
Date: Tue, 22 Apr 2025 10:44:33 +0000 [thread overview]
Message-ID: <F85259CF-8D1A-4464-A296-487B30A67ED1@arm.com> (raw)
In-Reply-To: <20250422025127.605-1-leimaohui@fujitsu.com>
On 22 Apr 2025, at 03:51, Lei Maohui <leimaohui@fujitsu.com> wrote:
>
> Error: Transaction test error:
> file /usr/share/gir-1.0/Gst-1.0.gir conflicts between attempted installs of lib32-gstreamer1.0-dev-1.26.0-r0.core2_32 and gstreamer1.0-dev-1.26.0-r0.core2_64
>
> fixed-size differs between 32 bit and 64 bit system
>
> $ diff /mnt/test/build_auh/tmp/work/core2-64-poky-linux/gstreamer1.0/1.26.0/image/usr/share/gir-1.0/Gst-1.0.gir /mnt/test/build_auh/tmp/work/core2-32-pokymllib32-linux/lib32-gstreamer1.0/1.26.0/image/usr/share/gir-1.0/Gst-1.0.gir
> 31864c31864
> < <array zero-terminated="0" fixed-size="8">
> ---
>> <array zero-terminated="0" fixed-size="12">
>
> The issue that "/usr/share is a architecture-independent location but contains architecture-dependent file", is
> a "long-known problem with gobject-introspection. You'll probably find an issue or three from 10 years ago about that"
> according to https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/4377
>
> We can found issue reported years ago, gstreamer community will not handle this issue for now
> https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues?search=multiarch
And I still reject this as being an inappropriate workaround: you shouldn’t have to use update-alternatives to build something unless desperately needed.
Following the search you provided we come across https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/323 for the general issue and the accepted MR https://gitlab.gnome.org/GNOME/gobject-introspection/-/merge_requests/63 that was filed by Kang Kai from Wind River.
This is not the solution. Putting the .gir into $libdir is the answer. See, for example, the Debian G-I policy: https://salsa.debian.org/gnome-team/gobject-introspection/-/blob/debian/latest/debian/policy.txt?ref_type=heads.
The interesting question is why Debian doesn’t feel the need to do this.
Ross
next prev parent reply other threads:[~2025-04-22 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 2:51 [OE-core] [PATCH] gstreamer1.0-dev: Fix install conflict when enable multilib Lei Maohui
2025-04-22 10:44 ` Ross Burton [this message]
2025-04-24 1:01 ` 回复: " Yiding Liu (Fujitsu)
2025-04-22 11:17 ` Ross Burton
2025-04-23 2:57 ` 回复: " Yiding Liu (Fujitsu)
-- strict thread matches above, loose matches on Subject: below --
2025-04-15 3:08 Lei Maohui
2025-04-17 9:19 ` Jose Quaresma
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=F85259CF-8D1A-4464-A296-487B30A67ED1@arm.com \
--to=ross.burton@arm.com \
--cc=leimaohui@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
/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