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

shared libs builds with 32 bit arch instaead of 64 bit #2888

Closed
o-murphy opened this issue Sep 4, 2023 · 4 comments
Closed

shared libs builds with 32 bit arch instaead of 64 bit #2888

o-murphy opened this issue Sep 4, 2023 · 4 comments

Comments

@o-murphy
Copy link

o-murphy commented Sep 4, 2023

Versions

  • Python: 10
  • OS: Android
  • Kivy: 2.2.1

Description

After commit 4d50d7d shared libs of cpython modules builds with 32 bit arch instaead of 64 bit

@RobertFlatt
Copy link
Contributor

I was unable to replicate this with

android.archs = arm64-v8a
p4a.branch = develop

@misl6
Copy link
Member

misl6 commented Sep 5, 2023

Hi @o-murphy , can you please add some more info about it ?

Is the hostpython3 or the python3 impacted (or both)?

If you're using buildozer, can you please attach your buildozer.spec file?
If you're using python-for-android, without the aid of buildozer, can you please post your full p4a cmd?
Are you running the toolchain on Linux or macOS ?

@o-murphy
Copy link
Author

o-murphy commented Sep 5, 2023

Hi @o-murphy , can you please add some more info about it ?

Is the hostpython3 or the python3 impacted (or both)?

If you're using buildozer, can you please attach your buildozer.spec file? If you're using python-for-android, without the aid of buildozer, can you please post your full p4a cmd? Are you running the toolchain on Linux or macOS ?

Now i'm testing it, i think it not depend by last commit, issue is occuring on random run on CI build via github workflow, some builds fails to launch cause this error, but buildozer.spec and .yml was not changed between commits

@Julian-O
Copy link
Contributor

There wasn't enough information provided to repro.

Closing as can't repro, but if the problem persists (after clearing caches and installing latest), please let us know with full debug logs.

@Julian-O Julian-O closed this as not planned Won't fix, can't repro, duplicate, stale Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants