-
Notifications
You must be signed in to change notification settings - Fork 678
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
Compile errors on ubuntu 16.04 #1262
Comments
Thanks for reporting. Could you please tell us what version of uwsgi are you building? |
This was 2.0.13, but it is the same error all the way back to 1.9.20.
|
@scs3jb open() call in uwsgi_tmpfd has the correct third argument here so looks like something bogus elsewhere. |
same here with ubuntu 16.04, virtualenv2.7 and plain |
my resolution was: remove pinned version 2.0.8 to latest stable |
If this helps anyone, the issue persisted in versions >=2.0 for me. 1.9 has installed successfully (the same setting as patroqueeet: ubuntu 16.04, virtualenv2.7) |
@b0ses what does gcc -v says? Have you tried creating a new virtualenv with python2.7? If you have another python version installed can you try with that one too? |
@xrmx I am able to make a new virtual environment but I get the same error with 'sudo pip install uwsgi'. Python3 results in the same as well. |
As an update, I was able to install uwsgi 2.0.12 in mostly the same environment (virtualenv, ubuntu server 16, python 2.7) with the main differences being I had updated my pypi mirrors (working offline) and was on Ubuntu 16.04.1 instead of the previous 16.04.02. |
I'm getting the same error. Environment:
Any idea? |
@tkaah nope, works perfectly fine on debian sid with the same software:
|
Using the Dockerfile below I was able to reproduce the compilation issue in versions up to uwsgi 2.0.10, although it succeeds in versions 2.0.11 and later.
Looking at the 2.0.11 changelog, this fixed bug looks like a potential culprit, since 16.04 defaults to gcc-5 while 14.04 uses gcc-4.8: https://github.com/unbit/uwsgi-docs/blob/master/Changelog-2.0.11.rst#bugfixes
Another potential culprit, since the issues are related to a function inlined from
In any case, using a version >= 2.0.11 should resolve the problem. |
Using clang was a successful workaround for me:
|
It is necessary to specify version 2.0.15 for uwsgi to overcome a bug: unbit/uwsgi#1262
@jnozsc yes we want! |
Looks like an issue with gcc?
The text was updated successfully, but these errors were encountered: