-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
WiP : CPython3 inclusion #1216
base: master
Are you sure you want to change the base?
WiP : CPython3 inclusion #1216
Conversation
Lotsa warnings..... Need to troubleshooting before opening PR, IF cross-build worked - Attempt to remove include from host system with upstream patches against 3.9.2 (debian-11 locally deployed python)
The builds fails at https://app.circleci.com/pipelines/github/tlaurion/heads/1205/workflows/4ad764c2-b1d4-4273-ba58-19cc322c44f0/jobs/10624?invite=true#step-103-3751, trying to link against host's libc instead of musl-cross-make's, even if specified properly in the module https://github.com/osresearch/heads/pull/1216/files#diff-51bef0474d1464907f19301711f3d641a3621d8d86d4f6072350c1bf290078b1R28.
Still, the following error happens since the wrong libc is picked (host vs musl-cross-make's).
Issue tracked under #689. This PR will stall until a fix is found, discussions can happen into referred tickets. |
This is still not working, and aimed at seeking help from the community into resolving packaging problems when crosscompiling python3 even today.
As of current state creating this draft, I am not able to force python using its own
--with-libc="$(musl-cross_libraries)"
which should point to musl-cross-make's libc.so. Python still attempts to link against host's libc, resulting in:Recommendations are sparse, and were documented prior into #233 #689.
When those problems are resolved, this will:
Fixes #233 #689