X86 64 linux gnu gcc failed with exit status 1

error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1 #585

Comments

yuanCabaal commented Jun 5, 2020

Hi,
when I was trying to run the command «pip3 install —user .» get the error in the title for: Building wheel for vmaf (setup.py) . error
Running setup.py install for vmaf . error

I followed closely the instruction of vmaf. Are there other packages that I have to install besides the ones mentioned in the documentation?

The text was updated successfully, but these errors were encountered:

1480c1 commented Jun 5, 2020

Try seeing if your distro provides a package similar to python-wheel

yuanCabaal commented Jun 7, 2020 •

python-wheel is already installed. Are you suggesting to use a different package instead of python-wheel?
I also added the error output:

ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -u -c ‘import sys, setuptools, tokenize; sys.argv[0] = ‘»‘»‘/tmp/pip-req-build-poc9k9wd/setup.py'»‘»‘; file='»‘»‘/tmp/pip-req-build-poc9k9wd/setup.py'»‘»‘;f=getattr(tokenize, ‘»‘»‘open'»‘»‘, open)(file);code=f.read().replace(‘»‘»‘\r\n'»‘»‘, ‘»‘»‘\n'»‘»‘);f.close();exec(compile(code, file, ‘»‘»‘exec'»‘»‘))’ bdist_wheel -d /tmp/pip-wheel-oeswf4g2
cwd: /tmp/pip-req-build-poc9k9wd/
Complete output (90 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.8
creating build/lib.linux-x86_64-3.8/vmaf
copying vmaf/routine.py -> build/lib.linux-x86_64-3.8/vmaf
copying vmaf/svmutil.py -> build/lib.linux-x86_64-3.8/vmaf
copying vmaf/config.py -> build/lib.linux-x86_64-3.8/vmaf
copying vmaf/init.py -> build/lib.linux-x86_64-3.8/vmaf
creating build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/writer.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/decorator.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/scanf.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/reader.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/interpolation_utils.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/plot.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/sigproc.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/misc.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/stats.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/kimchi.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/init.py -> build/lib.linux-x86_64-3.8/vmaf/tools
copying vmaf/tools/bd_rate_calculator.py -> build/lib.linux-x86_64-3.8/vmaf/tools
creating build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/result.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/adm_dwt2_py.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/mixin.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/executor.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/train_test_model.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/noref_feature_extractor.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/quality_runner.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/niqe_train_test_model.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/feature_extractor.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/h5py_mixin.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/matlab_quality_runner.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/feature_assembler.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/matlab_feature_extractor.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/raw_extractor.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/quality_runner_extra.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/asset.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/cross_validation.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/result_store.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/perf_metric.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/nn_train_test_model.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/local_explainer.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/init.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/proc_func.py -> build/lib.linux-x86_64-3.8/vmaf/core
copying vmaf/core/adm_dwt2_tools.py -> build/lib.linux-x86_64-3.8/vmaf/core
creating build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_vmafossexec_subsampling.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_vmaf_in_batch.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_toddnoiseclassifier.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_result_assembly.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_vmaf.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/ffmpeg2vmaf.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_psnr.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_testing.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/init.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_vmaf_training.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_vmaf_cross_validation.py -> build/lib.linux-x86_64-3.8/vmaf/script
copying vmaf/script/run_cleaning_cache.py -> build/lib.linux-x86_64-3.8/vmaf/script
running egg_info
creating vmaf.egg-info
writing vmaf.egg-info/PKG-INFO
writing dependency_links to vmaf.egg-info/dependency_links.txt
writing entry points to vmaf.egg-info/entry_points.txt
writing requirements to vmaf.egg-info/requires.txt
writing top-level names to vmaf.egg-info/top_level.txt
writing manifest file ‘vmaf.egg-info/SOURCES.txt’
reading manifest file ‘vmaf.egg-info/SOURCES.txt’
writing manifest file ‘vmaf.egg-info/SOURCES.txt’
copying vmaf/core/adm_dwt2_cy.c -> build/lib.linux-x86_64-3.8/vmaf/core
running build_ext
building ‘vmaf.core.adm_dwt2_cy’ extension
creating build/temp.linux-x86_64-3.8
creating build/temp.linux-x86_64-3.8/vmaf
creating build/temp.linux-x86_64-3.8/vmaf/core
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/local/lib/python3.8/dist-packages/numpy/core/include -I../libvmaf/src -I/usr/include/python3.8 -c vmaf/core/adm_dwt2_cy.c -o build/temp.linux-x86_64-3.8/vmaf/core/adm_dwt2_cy.o
In file included from /usr/local/lib/python3.8/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1832,
from /usr/local/lib/python3.8/dist-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /usr/local/lib/python3.8/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
from vmaf/core/adm_dwt2_cy.c:612:
/usr/local/lib/python3.8/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning «Using deprecated NumPy API, disable it with » «#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION» [-Wcpp]
17 | #warning «Using deprecated NumPy API, disable it with »
| ^

vmaf/core/adm_dwt2_cy.c:615:10: fatal error: ../../../libvmaf/src/feature/adm_tools.c: No such file or directory
615 | #include «../../../libvmaf/src/feature/adm_tools.c»
| ^

compilation terminated.
error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1

ERROR: Failed building wheel for vmaf

ChengHan111 commented Jun 12, 2020

I also got the same question about that. I wandering if there is a more specific answer to that? Thank you

1480c1 commented Jun 12, 2020

my best answer would be to try to see if your system differentiates between pip, pip2, and pip3, and make sure you have the right package for the pip you are using, for example, if pip —version returns something like (python 3.*) at the end, that signals to me that your distro’s default python version is 3, so you would just look for python-wheel in your package manager, however, if your system does not default to python 3 with its packages, you would need to look for something like python3-wheel .

I personally do not use the python side of vmaf and pretty much only use the libvmaf and vmafossexec provided, which only requires running make or using meson+ninja directly.

@li-zhi might have a better answer for your problem since he seems to be the main person modifying the python scripts

ChengHan111 commented Jun 12, 2020

I actually thinking I am facing this problem then I double check to make sure I have got python3-wheel already. Also I am in python 3.6.9 dev as well. Though my pip —version is in python2.7 I use pip3 all the time. Still facing the problem though

1480c1 commented Jun 12, 2020

Can you give me details such as what distro+version and what exact commands you used starting from git clone or download so I can try to reproduce?

ChengHan111 commented Jun 12, 2020

Thank you for helping me.
Here place the code:

sudo apt-get update -qq &&
sudo apt-get install -y
python3
python3-dev
python3-pip
python3-setuptools
python3-wheel
python3-tk

pip3 install —user .

I get stuck at —user . The error code is above the same as @yuanCabaal mentioned four days ago.
Running in Ubuntu 18.04.4 LTS with python 3.6-dev (in python3.6.9)

1480c1 commented Jun 12, 2020

does indeed reproduce the results.

It seems it might stem from the file python/vmaf/core/adm_dwt2_cy.pyx and the way pip builds stuff.

It seems the generated c file gets placed in a random pip temp dir under /tmp/pip- -build and it does not seem to call gcc from the current folder, so ../../../libvmaf/src/feature/adm_tools.c would not produce the correct path

1480c1 commented Jun 12, 2020

I do not know enough about python, setuptools, and cython to be able to code a fix for this right now

1480c1 commented Jun 12, 2020

It seems running

ChengHan111 commented Jun 12, 2020

I first run python3 setup.py install generating a c.file then pip3 install —user . gets no error. But still there is a problem when I try to run the testing part. When I run ‘./unitest’, there is still assertionerror, which says the vmaff_rc does not exist. And the testing part is almost all fail or error. I am wandering there might be something wrong when doing the setup.py process.
Here is my procedure:
apt update
apt install git g python3<,->
git clone https://github.com/Netflix/vmaf.git
cd vmaf/python
pip3 install cython
pip3 install -r requirements.txt
python3 setup.py install
pip3 install —user .

Then cd to the repository root and run
./unitest

This process still goes wrong, would u please run this line to double check for me? Thank you

1480c1 commented Jun 12, 2020

You need to run make in the vmaf directory with meson and ninja installed

ChengHan111 commented Jun 12, 2020

Okay I get this! I successfully run the test after I update my ninja! Thank you so much! This helps a lot!

yuanCabaal commented Jun 13, 2020

Do you have to run make first and then install the python code?

1480c1 commented Jun 13, 2020

The make command was only needed because he wanted to run the unit tests

nasirhemed commented Jun 15, 2020 •

I was able to set it up using python setup.py install but I was facing a couple of issues:

• The binaries are not added in pip3’s local packages
• I am not able to run pip3 install —user . after running python setup.py install
• I am getting the following error when I run vmaf/python/vmaf/script/run_vmaf.py

Any ideas on how to overcome this? I’m running through the same issue on docker as well

slhck commented Jun 16, 2020

@li-zhi Any idea what was changed that broke the Python build? I also cannot install the Dockerfile anymore:

It seems this is related to the Cython requirement, and running make requires cython , even though it is only installed later when installing the Python requirements.

Источник

сценарий установки вышел с ошибкой: команда ‘x86 64-linux-gnu — gcc’ завершилась неудачно со статусом выхода 1

когда я пытаюсь установить odoo-server , Я получил следующую ошибку:

кто-нибудь может помочь мне решить эту проблему?

26 ответов:

Python.ч ничего, кроме заголовка файла. Он используется GCC для создания приложений. Вам необходимо установить пакет под названием python-dev. Этот пакет включает в себя заголовочные файлы, статическую библиотеку и средства разработки для построения модулей Python, расширения интерпретатора Python или встраивания Python в приложения.

или

попробуйте установить эти пакеты.

я столкнулся с той же проблемой в колледже, установив Linux Mint для основного проекта моего последнего года, третье решение ниже работало для меня.

, когда встретив эта ошибка обратите внимание, прежде чем ошибка может сказать, что вы отсутствует пакет или файл заголовка, вы должны найти их и установить их и проверить, если он работает. (например, ssl — > libssl)

на Python 2.x использование:

для Python 2.7 использование:

на Python 3.x использование:

на Python 3.4 использование:

на Python 3.5 использование:

на Python 3.6 использование:

Источник

error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1 #565

Comments

kramer65 commented Sep 17, 2015

I’m trying to install bpython a a fairly fresh Ubuntu 14.04 box using sudo pip install bpython . But this ends in the errors below.

So I made sure I had python-dev installed and also build-essential is already the newest version. But the problem persists. Any idea what the problem could be?

c/_cffi_backend.c:13:17: fatal error: ffi.h: No such file or directory
#include
^
compilation terminated.
error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1

The text was updated successfully, but these errors were encountered:

sebastinas commented Sep 17, 2015

Make also sure that you have libffi-dev installed or install the corresponding python-cffi packages.

kramer65 commented Sep 18, 2015

Thanks, installing libffi-dev indeed seemed to solve that.

after having fixed that, it started complaining about openssl/aes.h , so I installed libssl-dev , after which I could finally install bpython using the regular sudo apt-get install bpython .

Thanks for the help!

marcel060 commented Jun 7, 2020

python setup.py build
running build
running build_py
running build_ext
building ‘cpyrit._cpyrit_cpu’ extension
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-uC7NI8/python2.7-2.7.18=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c cpyrit/_cpyrit_cpu.c -o build/temp.linux-x86_64-2.7/cpyrit/_cpyrit_cpu.o -Wall -fno-strict-aliasing -DVERSION=»0.5.1″ -maes -mpclmul
cpyrit/_cpyrit_cpu.c:39:10: fatal error: zlib.h: No such file or directory
39 | #include
| ^

compilation terminated.
Failed to build; Compiling without AES-NI
building ‘cpyrit._cpyrit_cpu’ extension
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-uC7NI8/python2.7-2.7.18=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/include/python2.7 -c cpyrit/_cpyrit_cpu.c -o build/temp.linux-x86_64-2.7/cpyrit/_cpyrit_cpu.o -Wall -fno-strict-aliasing -DVERSION=»0.5.1″
cpyrit/_cpyrit_cpu.c:39:10: fatal error: zlib.h: No such file or directory
39 | #include
| ^

compilation terminated.
error: command ‘x86_64-linux-gnu-gcc’ failed with exit status 1 CAN SOMEONE HELP PLSS

sebastinas commented Jun 7, 2020

This isn’t the bug tracker for cpyrit.

If you are on a Debian-based system, install zlib1g-dev. Otherwise check which packages provides the zlib development files for your distribution.

Источник