From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 2/3] rpi-userland: fix opengl library symlinks
Date: Sat, 25 Mar 2017 15:25:07 +0100 [thread overview]
Message-ID: <20170325152507.3a17a336@free-electrons.com> (raw)
In-Reply-To: <20170322225104.32xu2q6fhyoph4fg@gportay>
Hello,
On Wed, 22 Mar 2017 18:51:04 -0400, Ga?l PORTAY wrote:
> > Ah, it uses dlopen() on specifically libEGL.so.1 and libOpenGLES.so.2,
> > OK. Then it makes sense. Maybe your patch should be submitted upstream
> > to rpi-userland?
>
> I am on it.
>
> I made a PR on github.
As was said in https://github.com/raspberrypi/userland/pull/379, the PR
you have submitted changes the SONAME of the library, so any binary
already built against rpi-userland before your change will no longer
work after your change. Your suggestion to run ldconfig is irrelevant.
When you link against a library, the SONAME of this library gets
encoded into a NEEDED entry of the thing (program or library) that
links against this library. Then at runtime, the dynamic loader goes
through those NEEDED entries to load the shared libraries that the
program needs. So if the NEEDED entry of a program no longer points to
an existing library, you broke binary compatibility.
So maybe we simply need some symbolic links to be created:
libEGL.so.1 -> libEGL.so
libGLES.so.2 -> libGLES.so
This way, qt5webengine will be able to find the EGL/OpenGLES
implementation, but the rpi-userland libraries SONAME remains the same.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-25 14:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 18:13 [Buildroot] [RFC 0/3] Qt WebEngine support Gaël PORTAY
2017-03-22 18:13 ` [Buildroot] [RFC 1/3] qt5webengine: new package Gaël PORTAY
2017-04-18 16:04 ` Gaël PORTAY
2017-05-23 1:46 ` jsmith
2017-06-30 6:19 ` gomsis
2017-07-04 18:39 ` Gaël PORTAY
2017-07-07 5:33 ` Brent Sink
2017-07-07 18:58 ` Gaël PORTAY
2017-07-08 10:48 ` gomsis
2017-07-14 13:26 ` gomsis
2017-07-14 17:38 ` Gaël PORTAY
2017-07-17 5:40 ` gomsis
2017-07-17 5:42 ` gomsis
2017-03-22 18:13 ` [Buildroot] [RFC 2/3] rpi-userland: fix opengl library symlinks Gaël PORTAY
2017-03-22 21:54 ` Thomas Petazzoni
2017-03-22 22:38 ` Gaël PORTAY
2017-03-22 22:47 ` Thomas Petazzoni
2017-03-22 22:51 ` Gaël PORTAY
2017-03-25 14:25 ` Thomas Petazzoni [this message]
2017-04-11 16:30 ` Gaël PORTAY
2017-03-22 18:13 ` [Buildroot] [RFC 3/3] configs: new raspberrypi3 qt5 config Gaël PORTAY
2017-03-22 21:21 ` [Buildroot] [RFC 0/3] Qt WebEngine support Peter Seiderer
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=20170325152507.3a17a336@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox