Skip to content
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

purego.Dlopen fails on Galaxy A02s #262

Closed
1 of 6 tasks
hajimehoshi opened this issue Aug 1, 2024 · 2 comments · Fixed by #263
Closed
1 of 6 tasks

purego.Dlopen fails on Galaxy A02s #262

hajimehoshi opened this issue Aug 1, 2024 · 2 comments · Fixed by #263
Labels
bug Something isn't working

Comments

@hajimehoshi
Copy link
Member

PureGo Version

v0.8.0-alpha.3

Operating System

  • Windows
  • macOS
  • Linux
  • FreeBSD
  • Android
  • iOS

Go Version (go version)

go version go1.22.5 darwin/arm64

What steps will reproduce the problem?

Call purego.Dlopen("libGLESv2.so", purego.RTLD_LAZY|purego.RTLD_GLOBAL) on Android

What is the expected result?

An so file is loaded

What happens instead?

Error:

invalid flags to dlopen: 101

Anything else you feel useful to add?

Galaxy A02s has 32bits Android OS though the CPU is 64bit. Also, Android has different definitions for RTLD_* for 32bits.

Even though I used C's RTLD_*, another crash happened. I am not sure when this happened. Maybe loading a symbol?

See also hajimehoshi/ebiten#3052

@hajimehoshi hajimehoshi added the bug Something isn't working label Aug 1, 2024
@TotallyGamerJet
Copy link
Collaborator

This is such a strange case where it's a 64Bit CPU but a 32bit OS.

@hajimehoshi
Copy link
Member Author

Indeed...

hajimehoshi added a commit to hajimehoshi/ebiten that referenced this issue Aug 5, 2024
This is basically a revert for 297efea.
This updates PureGo for the Android issue.

Updates #3052
Updates ebitengine/purego#262
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants