是否可以提供yolox的whl包
我在linux gcc7.3.0上尝试安装yolox但是无法成功
In file included from /usr/local/python3.7/lib/python3.7/site-packages/pybind11/include/pybind11/complex.h:14:0,
from /usr/local/python3.7/lib/python3.7/site-packages/pybind11/include/pybind11/numpy.h:13,
from /home/manas/YOLOX-0.3.0/yolox/layers/cocoeval/cocoeval.h:4,
from /home/manas/YOLOX-0.3.0/yolox/layers/cocoeval/cocoeval.cpp:2:
/usr/include/c++/7.3.0/complex:800:5: internal compiler error: Illegal instruction
{ return std::log(__z) / log(_Tp(10.0)); }
是否对gcc版本有要求?能否提供一下whl包
We have provide a sdist whl for yolox 0.3.0. I'm using gcc version 8.4 and gcc version 7.3
should work. Could you post the full log here?
I wonder what if you compile a c file like hello_world.c
We have provide a sdist whl for yolox
0.3.0
Where ?
python3 -m pip install yolox==0.3.0
https://pypi.org/project/yolox/#files no whl here
It's sdist not bdist.
Why dont you provide bdist
Because we have to pack our code for every version of python since py3.6 (and maybe we should check every single platform also). BTW, I wonder that could you compile a c file like hello_world.c on your machine?
By the way , i build it successfully on the other machine with gcc 7.4.0
BTW, I wonder that could you compile a c file like hello_world.c on your machine?
I am not a C engineer but only a Python engineer.
By the way , i build it successfully on the other machine with gcc 7.4.0
What does it refer to? YOLOX or hello.c?
By the way , i build it successfully on the other machine with gcc 7.4.0
What does
itrefer to? YOLOX or hello.c?
YOLOX
Well, if bdist whl is needed, we could provide such a feature in the next release.
Thank you , you see that the users can have a perfect runtime environment easily,but it is hard to make them setup a perfect compiling environment . So it is good for you to provide bdist wheel. As other projects did, you can use something like github-flow to build wheel accross the platforms and py versions easily.
For right now,i have tried gcc 4.8.5,7.3.0, 7.4.0 and 10.3.0. 4.8.5 can not meet the minimum condition. 7.3.0 failed. 7.4.0 10.3.0 succed. Maybe you should list this condition on you doc?