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

Build fails on Alpine when building in not a x86 architecture #2414

Closed
rgdoliveira opened this issue Oct 26, 2017 · 7 comments · Fixed by #2427
Closed

Build fails on Alpine when building in not a x86 architecture #2414

rgdoliveira opened this issue Oct 26, 2017 · 7 comments · Fixed by #2427

Comments

@rgdoliveira
Copy link

Long story short

When trying to build aiohttp version 2.3.1 in Alpine (ppc64le and s390x architectures) the build fails at Alpine stripping part because it tries to strip "_http_parser.cpython-36m-x86_64-linux-gnu.so" shared object that is shipped in source code and fail in any architecture different from x86.

I guess the "_http_parser.cpython-36m-x86_64-linux-gnu.so" should not be shipped in the source code

Steps to reproduce

  • Clone Alpine aports project
  • build py3-aiohttp project (community/py3-aiohttp) with command abuild -r

Your environment

Alpine Linux 3.6.2 (ppc64le or s390x)

algitbot pushed a commit to alpinelinux/aports that referenced this issue Oct 26, 2017
Manually remove _http_parser.cpython-36m-x86_64-linux-gnu.so shared
object that is shipped in source code and make strip fails in not
x86 architectures.

Bug opened upstream: aio-libs/aiohttp#2414
@asvetlov
Copy link
Member

Good catch!
@webknjaz could you take a look? Or maybe @rgdoliveira could find a time for fix?
Checking build in Alpine would be nice but we should remove .so from tarball at least.

The PR should be done against 2.3 branch, I want make a new bugfix release.

@webknjaz webknjaz self-assigned this Oct 26, 2017
@webknjaz
Copy link
Member

webknjaz commented Oct 26, 2017

@rgdoliveira @asvetlov I think, including smth like find -name *.so -type f -delete into our release process would fix this. Still I'll need some time for testing other approaches as well. For example, we could exclude it from manifest (https:/aio-libs/aiohttp/blob/ca575f9/MANIFEST.in#L12-L18) or/and improve integration with setuptools-git, which seems to be added at some point (

setuptools-git==1.2
), but not configured completely.

@asvetlov
Copy link
Member

Let's just add explicit exclusion rule in MANIFEST.in as hotfix.
We could return to discussion about setuptools-git usage later.
I don't feel we need it but maybe @webknjaz is true.
He was true many times regarding to our deployment process.

Anyway let's fix manifest and discuss future improvements later.

@RemiCardona
Copy link

Just a friendly poke to let you guys know I had to locally fix this issue by re-uploading 2.3.1 in my private pypi repo as 2.3.1+custom. This tar.gz was generated using python setup.py sdist in a fresh git clone and it works just great.

@asvetlov
Copy link
Member

@RemiCardona thank for comment but we should fix our deployment process.

@asvetlov
Copy link
Member

Fixed by 8622d6c
Please wait for bugfix release

@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that [new issue].
[new issue]: https:/aio-libs/aiohttp/issues/new

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants