-
-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RIVE box64 + gl4es SIGSEGV libc.so.6 #1151
Comments
To get to the ground of this issue I tried to get back to the most simple examples. For testing I used this simple SDL2 + GLES file
I compiled it first in my aarch64 chroot and then tested it on my device. Exports for ld_library is set
|
Out of curiosity I tried to do the same test on box86
|
Did some additional tests with LD_DEBUG=libs It lists all search paths for the other libs just fine but never even attempts to load libgles2.v2
|
Okay so we only have wrappers for libGL and libGLX and not libGLESv2. Makes sense that it would not work and most desktop apps don't use libGLESv2 directly. I will try with opengl2 apps in combination with gl4es. |
Hey ptitseb!
I'm testing box64 on my rk3326 chipset on AmberELEC after good results i had with box86.
I previously did some tests with box64 on world of goo where both the i386 aswell as the amd64 binaries were present. But could not get it to run then. Now i tried this one. Maybe you have an idea what's going on.
Box64 and gl4es built from latest commit.
GL4ES via -DNOX11=ON -DGLX_STUBS=ON -DEGL_WRAPPER=ON -DGBM=ON
Box64 via -DARM64=ON -DARM_DYNAREC=ON
Game run via
LDD of the binary
Log:
And log without any libGL.so.1
On the rk3326 we don't have opengl everywhere so only opengles up to 3
The text was updated successfully, but these errors were encountered: