ERROR: Failed building wheel for uwsgi #2232
Comments
I get this error when running «pip install uwsgi» in a conda python 3.8 environment:
The text was updated successfully, but these errors were encountered:
Looks like an issue with your python:
ld: in /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o), could not parse object file /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o): ‘Unknown attribute kind (61) (Producer: ‘LLVM10.0.0’ Reader: ‘LLVM APPLE_1_1001.0.46.4_0′)’, using libLTO version ‘LLVM version 10.0.1, (clang-1001.0.46.4)’ for architecture x86_64
Thanks for the response, @xrmx ! I downgraded to python 3.7 and it worked just fine. Do you think it’s some issue between conda and my Mac? I guess I could try using virtualenv rather than conda and see if I get different results.
Looks like an issue with your python:
ld: in /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o), could not parse object file /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o): ‘Unknown attribute kind (61) (Producer: ‘LLVM10.0.0’ Reader: ‘LLVM APPLE_1_1001.0.46.4_0′)’, using libLTO version ‘LLVM version 10.0.1, (clang-1001.0.46.4)’ for architecture x86_64
I had the same problem,
But I can’t do a downgrade because the company needs Python 3.8
Looks like an issue with your python:
ld: in /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o), could not parse object file /Users/pcurtis/miniconda3/envs/nginx3/lib/python3.8/config-3.8-darwin/libpython3.8.a(getargs.o): ‘Unknown attribute kind (61) (Producer: ‘LLVM10.0.0’ Reader: ‘LLVM APPLE_1_1001.0.46.4_0′)’, using libLTO version ‘LLVM version 10.0.1, (clang-1001.0.46.4)’ for architecture x86_64
I had the same problem,
But I can’t do a downgrade because the company needs Python 3.8
Please, I had the same problem. Do you find decision?
As a workaround, you can install uwsgi using conda forge: https://anaconda.org/conda-forge/uwsgi.
apt-get install build-essential python doesn’t detect python 3. I followed these commands:
/Project$ sudo apt-get update
sudo apt-get upgrade
sudo apt-get install build-essential python
sudo apt-get install python-dev
sudo apt-get install python3-all-dev
sudo apt-get install uwsgi-plugin-python3
pip install uwsgi
pip install uwsgi ( to validate that it was installed)
original error:
Collecting uwsgi
Using cached uwsgi-2.0.20.tar.gz (804 kB)
Building wheels for collected packages: uwsgi
Building wheel for uwsgi (setup.py) . error
ERROR: Command errored out with exit status 1:
I’m having the same issue, I tried the conda forge workaround but it kept loading at Solving environment and just keeps loading forever. I even changed my conda environment and the error still persisted.
I tried this workaround again and I got the following:
So I tried downgrading to python 3.9 and retried installing uwsgi again using pip, but still got back to the same previous error as in the beginning:
Linking error when installing uwsgi with pip in virtualenv #1516
Comments
Hello,
I’m getting my Django application ready for production, as a requisite I am trying to install uwsgi in a virtual env using the following command
During the install when it is linking I get the following error:
From what I know, this is a link error, I thought it cannot find openssl, but I have openssl installed — I think. I’m using Ubuntu 16.04 x86_64. Any help would be appreciated. Thank you! 🙂
The text was updated successfully, but these errors were encountered:
I installed openssl using the following command
Hi, you have to install libssl-dev (or equivalent)
Hi! I just ran this, it says its already installed.
I retried installing but no luck. Let me know If you need any other info. 🙂
Same problem here, libssl-dev is already installed.
Same problem here, install uwsgi 2.0.15 in pypy 5.9 and python 3.5.3 in Ubuntu 16.04
openssl 1.0.2g
Same problem, I use CentOS 7.4, anaconda3 v5.0.1, in a virtual environment of python 3.5
my error info
If I create a virtual environment with conda create -n py27 python=2.7 , I can install uwsgi by pip install uwsgi correctly!
CentOS 7.2 and CentOS 7.3 can install correctly!
CentOS 7.4 with python 3.4 also does not work, like above in python 3.5, but has different error hint!
I almost want to give up, then I find this page: https://github.com/conda-forge/uwsgi-feedstock
Now you can install uwsgi though conda:
conda config —add channels conda-forge
conda install uwsgi
looks like an anaconda3 issue.
Same problem with miniconda3
It seems like we have a solution to this. Thanks to @OnlyBelter 👍 Closing this issue therefore! 🎉
pip install uwsgi error, I’m not sure if this is related to pip #568
Comments
Hi, I’m getting Errors installing uwsgi using pip on rc-buster, rc-alpine, rc-slim as well as with alipine and slim.
The installation on python:buster runs fine.
The trace is very large so here is the final message:
This is part of the log: Building wheel for uWSGI (setup.py): finished with status ‘error’
I’m not sure if this triggered the error but apparently this function is deprecated
The text was updated successfully, but these errors were encountered:
oh BTW I tried installing the packages: python3.7-dev build-essential and linux-headers-amd64 but the error didn’t change obviously because I was using pip.
I understand that this looks like an issue with pip but it works on python:buster so I think this is probably associated with this project somehow. Anyway I will appreciate your help
And pip install mod-wsgi-standalone also throws an error in standalone images.
- With booster and rc-booster it never start the build
But with rc-alpine I get the following error
Am I missing something?
Am I sopposed to add dev packages in the latest images available at hub.docker?
So you only experience the issues on the rc versions with uwsgi?
python:rc-buster,
python:rc-alpine,
python:rc-slim,
python:alipine,
python:slim
with both uwsgi and mod-wsgi-standalone (I didn’t try pip install mod-wsgi because I didn’t have httpd installed)
Note that pip install uwsgi works fine on python:buster.
The rc versions are all currently the (unreleased) 3.10 series, which probably isn’t supported by uwsgi yet — the slim and alpine images are optimized for size, so in order to install modules that need a compiler, you’ll need to install one (the buster non-slim images already contain the necessary compiler).
Thank you.
I opened this issue because I thought those are release candidates.
I understand these images are lightweight versions but it’s not clear which packages should I use i.e. python3.x-dev or build essentials and build uwsgi form source which loose the entire purpose of containers.
Should I close the issue?
Do you think I should open an issue in pypi? Because they would tell me that it’s not their fault that an image doesn’t have the appropriate packages in order to use pip
No, this is a usability/understand gap, not an issue with the image or pip or pypi, frankly. 😅
What I’d suggest is asking for help understanding how to accomplish what you’re looking for from a dedicated support forum such as the Docker Community Forums, the Docker Community Slack, or Stack Overflow. 👍
Error in pip install uwsgi in macos x #1364
Comments
Problem installing uwsgi in mac os x 10.11 El capitan with xcode version 8 and python version 3.5.2 using
pip install uwsgi
Following is the error message
The text was updated successfully, but these errors were encountered:
FWIW: I’ve tried modifying buildconf/default.ini adding xml = expat and it builds.
I’ve got the same problem 🙁
+1 @unbit Please check this question
People, github added a way to add your reaction to the original submission so you can avoid annoying +1 . Please use them.
Same here, tried to add
and it does not build
In this way, it worked for me.
brew unlink libxml2
brew uninstall libxml2
brew install —with-python libxml2
brew link libxmls2 —force
pip install uwsgi
Possibly it might work just running the command:
brew install —with-python libxml2
@ilubnon note that you have a type-o in the link line (libxmls2 instead of libxml2), but anyway it seems unrelated. I think this is having something to do with the fact of running a new XCode with OSX 10.11, which does not have to seem to have this /usr/lib/system/libsystem_symptoms.dylib file.
seems unrelated, but works for me as well (didn’t previously have libxml2 ) but installing it first allows uwsgi to build as well
Tried right now – does not work:
I was able to successfully uninstall and reinstall libxml2, but I’m still unable to install uwsgi. I’m on Python 3.6.0.
@svetlyak40wt that appears to be a problem with your homebrew formula, I get a slight different url appearing in my copy which is found. try again after a brew update
@AlJohri difficult to diagnose from what you have said. maybe it’s not finding your homebrew libraries, try with:
(assuming you’re using a bourne shell and have homebrew in the standard place)
Going thru stack overflow, this works for me
Some people are saying that it’s due to invalid references in Xcode, I have no idea.
I don’t have a solution, just some words regarding the general problem I had. I was working on OSX 10.11 (El Capitan) and already installed XCode 8. However for El Capitan XCode 8 does not ship with command-line tools and looks like support is not comming. My solution was to upgrade to OSX 10.12 (Sierra), update XCode and then it works.
It works after brew upgrades to new packages.
uWSGI Install and Use Issues
Contents
My notes on several issues when installing and running uWSGI.
pip install uwsgi error
When I try to install uwsgi using pip, there are compilation errors. After some search, based on discussions here, I find the cause of this issue is that the version of gcc is too high. I am using Ubuntu 18.04, and the default gcc version is 7.4.0.
Based on this post, the minimum gcc we can install from the default Ubuntu 18.04 remote repo is gcc-4.8. There is no gcc-4.7 available for install. It turns out that gcc-4.8 works fine:
Then we need to change the gcc command to point to gcc-4.8:
After that, I can install uwsgi successfully using pip. Finally, let’s revert the gcc version to its old state:
uwsgi can not find shared object
I use the following command to install uwsgi with conda:
When I run uwsgi —version , I see the following error message:
error while loading shared libraries: libicui18n.so.58: cannot open shared object file: No such file or directory
The solution is to run conda install icu=58 , ref here.
uwsgi segmentation fault
I am using uwsgi 2.0.18 (installed via conda install -c conda-forge uwsgi ) with python 3.7.7 from Miniconda. When I use uwsgi to server a simple Flask application, I see segmentation errors below:
My MWE flask application:
The uwsgi command to run flask application:
The scrip to test this service:
When I request the service, I see the above segmentation errors.
If I create a conda virtual env with python version 3.6:
run the service using uwsgi and request again, the error disappears.
If I do not use concurrent.futures , I see no errors both for python 3.7 and python 3.6. I am not knowledgeable enough to know the exact cause of this issue. It seems there is some compatibility issue with uwsgi, python version and concurrent package.
symbol not found on macOS
I am using Python 3.7 installed via Anaconda, and uWSGI is installed via pip. When I run my simple Flask application, I see the following error:
This seems to be a compatibility issue between uWSGI and Anaconda python. There are two solutions:
Uninstall uWSGI installed via pip and install it using conda:
Using Python 3.6 with uWSGI. We can create a new virtual env with Python 3.6.5 and intall uWSGI inside.
After that, activate the virtual env and install uWSGI inside: