Error command arm linux gnueabihf gcc failed with exit status 1

«command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1» при установке PycURL

Пытаюсь установить PycUCL через pip install pycurl . Выдает следующую ошибку:

error: command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1.

arm-linux-gnueabihf-gcc также не получается установить:

E: Unable to locate package gcc-arm-linux-gnueabi

2 ответа 2

Свою проблему я решил, не хватало следующего:

Спасибо всем кто пытался помочь.

Судя по приведенным логам сборки у вас компилятор вызывается с неподдерживаемым флагом (stack-protector-strong). Тут пишут что может помочь обновление gcc или изменение файла. Возможно, получится просто слить исходники и собрать их самому

Всё ещё ищете ответ? Посмотрите другие вопросы с метками python debian gcc arm или задайте свой вопрос.

Похожие

Подписаться на ленту

Для подписки на ленту скопируйте и вставьте эту ссылку в вашу программу для чтения RSS.

дизайн сайта / логотип © 2021 Stack Exchange Inc; материалы пользователей предоставляются на условиях лицензии cc by-sa. rev 2021.10.8.40416

Нажимая «Принять все файлы cookie» вы соглашаетесь, что Stack Exchange может хранить файлы cookie на вашем устройстве и раскрывать информацию в соответствии с нашей Политикой в отношении файлов cookie.

Источник

error: command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1 on RPi 3b when ‘python setup.py install’ #294

Comments

JayJoeSeventh commented Apr 30, 2018

I wanted to ‘import neopixel’ from anywhere, so I try to do the installation as shown. but it fails with error ‘arm-linux-gnueabihf-gcc’.

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

ghost commented May 9, 2018

Hi!
I had same problem.
But I tried to follow the steps of this https://learn.adafruit.com/neopixels-on-raspberry-pi and then I can build this without problem.
I think that solution is install «scons»:
sudo apt-get update
sudo apt-get install build-essential python-dev git scons swig

FuriosoJack commented Aug 23, 2018

For those that have not worked at all you have to install these packages

sudo apt-get install libzbar-dev libzbar0

rsengar3 commented Sep 16, 2018

I tried all of the above but still has same problem?

KEINOS commented Nov 2, 2018

I think you need to install python-dev too. In order to let gcc compile the Python extensions.

Sorry if it’s not the case.

tonytanjk commented Jan 3, 2019

I tried everything but it’s a fail

tonytanjk commented Jan 5, 2019

sudo apt-get install portaudio19-dev.
Try this

chrisdimoff commented Mar 22, 2019

Ensure SPI is enabled in raspi_config cd rpi_ws2811x && run scons try again be happy?

tlilianas commented Jul 31, 2019

this is what you are looking for guys :
sudo apt install -y python python-pip libffi-dev python-backports.ssl-match-hostname
sudo pip install docker-compose

jvanlangen commented Sep 20, 2019

Too bad, still:
Building wheel for cryptography (PEP 517) . error

erm3nda commented Dec 12, 2019

pawKer commented Dec 12, 2019

1. Ensure SPI is enabled in raspi_config
2. cd rpi_ws2811x && run scons
3. try again
4. be happy?

Just putting this out here in case it might help someone, this fixed it for me. I was getting the same error because I hadn’t run the scons command in the rpi_ws281x folder before running python setup.py build and python setup.py install . Exactly like @chrisdimoff says above.

maulalwi commented Jun 16, 2020

sudo apt install clang -y

rahulshyokand commented Jun 28, 2020

These Commands Fixed Similar Issue on my Rpi 3b

Note: These installations may not have any problem because some are already installed and some are not.
sudo python3 -m pip install —upgrade pip
sudo python3 -m pip install pyparsing==2.1.0
sudo python3 -m pip install pyparser==1.0
sudo apt-get install libffi-dev
sudo apt-get install libzbar-dev
sudo apt-get install clang -y

sudo apt-get install python3-dev
sudo apt-get install libssl-dev

Problem seems to be in cffi package

Following command also installs cffi package which will test installation
sudo python3 -m pip install cryptography==2.2.2
Alternativly you can try
sudo python3 -m pip install cffi

Here is the potential Error which gets solved

The issue in includes of openssl.h and python.h were solved

Источник

(install) command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1 #3

Comments

ash73 commented Jul 10, 2018

Hi, I cloned the git repository to my rPi2 and entered:
sudo python setup.py install

After doing some work it generates the error:
command ‘arm-linux-gnueabihf-gcc’ failed with exit status 1

The full output is:
running install
running bdist_egg
running egg_info
creating python/VL53L1X.egg-info
writing python/VL53L1X.egg-info/PKG-INFO
writing top-level names to python/VL53L1X.egg-info/top_level.txt
writing dependency_links to python/VL53L1X.egg-info/dependency_links.txt
writing manifest file ‘python/VL53L1X.egg-info/SOURCES.txt’
reading manifest file ‘python/VL53L1X.egg-info/SOURCES.txt’
reading manifest template ‘MANIFEST.in’
writing manifest file ‘python/VL53L1X.egg-info/SOURCES.txt’
installing library code to build/bdist.linux-armv7l/egg
running install_lib
running build_py
creating build
creating build/lib.linux-armv7l-2.7
copying python/VL53L1X.py -> build/lib.linux-armv7l-2.7
running build_ext
building ‘vl53l1x_python’ extension
creating build/temp.linux-armv7l-2.7
creating build/temp.linux-armv7l-2.7/api
creating build/temp.linux-armv7l-2.7/api/core
creating build/temp.linux-armv7l-2.7/api/platform
creating build/temp.linux-armv7l-2.7/python_lib
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_api_calibration.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_api_calibration.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_core.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_core.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_core_support.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_core_support.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_api_core.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_api_core.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_api_preset_modes.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_api_preset_modes.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_silicon_core.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_silicon_core.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_register_funcs.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_register_funcs.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_wait.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_wait.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_error_strings.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_error_strings.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_api_strings.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_api_strings.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/core/vl53l1_api.c -o build/temp.linux-armv7l-2.7/api/core/vl53l1_api.o
arm-linux-gnueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. -Iapi/core -Iapi/platform -I/usr/include/python2.7 -c api/platform/vl53l1_platform.c -o build/temp.linux-armv7l-2.7/api/platform/vl53l1_platform.o
api/platform/vl53l1_platform.c:279:1: warning: multi-line comment [-Wcomment]
//#define trace_print(level, . )
^
api/platform/vl53l1_platform.c:283:1: warning: multi-line comment [-Wcomment]
//#define trace_i2c(. )
^
api/platform/vl53l1_platform.c: In function ‘VL53L1_WaitValueMaskEx’:
api/platform/vl53l1_platform.c:321:2: error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode
for(int32_t x = 0; x

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

urbie-mk2 commented Jul 11, 2018 •

@ash73
try before:
export CXXFLAGS=»-std=c++11″
export CFLAGS=»-std=c99″

ash73 commented Jul 11, 2018

Still fails with the same error 🙁

Gadgetoid commented Jul 13, 2018

You could try adding it to the Makefile, IE:

ash73 commented Jul 13, 2018

Still fails with the same error. Am I missing some dependencies?

Gadgetoid commented Jul 13, 2018

You could possibly cheat and edit api/platform/vl53l1_platform.c to remove the declaration outside of the for loop.

You’re not missing a dependency, just my Makefile isn’t particularly friendly to your version of GCC (I’m using 6.3.0-18+rpi1+deb9u1).

Gadgetoid commented Jul 13, 2018

Curious, that change to the Makefile gets me building with gcc-4.4 , sure you’re changing it in the right place?

ash73 commented Jul 13, 2018 •

I copied and pasted your text into the file «Makefile» in the vl53l1x-python folder, I think the only bit that changed was adding -std=c99 to the end of the line starting CFLAGS :=

I looked at api/platform/vl53l1_platform.c but the declaration is different in mine:

Not sure what to change / remove.

ash73 commented Jul 13, 2018

gcc (Raspbian 4.9.2-10+deb8u1) 4.9.2

Gadgetoid commented Jul 16, 2018

If I install gcc-4.9 and build with cc=/usr/bin/gcc-4.9 make then it fails without -std=c99 , but if I add -std=c99 back in it works fine. You might be able to git pull since I’ve tweaked this into the Makefile upstream, but it sounds like you’re editing in the right place. I’m baffled as to why that flag isn’t picked up.

When you run Make what does the first line that appears say? It should have that flag listed.

As a crude hack you could try «CC=/usr/bin/gcc-4.9 -std=c99» make or «CC=/usr/bin/gcc -std=c99» make

In your case changing:

May work, but it also might just reveal other compiler issues that the -std=c99 flag should be fixing.

ash73 commented Jul 16, 2018

I tried again from scratch, deleting the vl53l1x-python folder and re-downloading it, the flag -std=c99 is in Makefile, but it still fails with the same error.

I tried updating api/platform/vl53l1_platform.c as described above, it proceeds but reports several other compiler errors, as you expected.

If I just enter make at the command prompt, it says:
cc -Iapi/core -Iapi/platform -std=c99 -fPIC -shared -o libvl53l1_api.a api/core/vl53l1_api_core.c api/core/vl53l1_error_strings.c api/core/vl53l1_api.c api/core/vl53l1_core_support.c api/core/vl53l1_wait.c api/core/vl53l1_api_calibration.c api/core/vl53l1_core.c api/core/vl53l1_api_preset_modes.c api/core/vl53l1_api_debug.c api/core/vl53l1_register_funcs.c api/core/vl53l1_api_strings.c api/core/vl53l1_silicon_core.c api/platform/vl53l1_platform.c
api/platform/vl53l1_platform.c: In function ‘VL53L1_WaitMs’:
api/platform/vl53l1_platform.c:294:2: warning: implicit declaration of function ‘usleep’ [-Wimplicit-function-declaration]
usleep(wait_ms * 1000);
^

If I enter make a second time, it says:
make: ‘libvl53l1_api.a’ is up to date.

As you can see, I don’t really know what I’m doing. I can read the sensor on an Arduino anyhow and pass the data to the Pi. Thanks for trying.

urbie-mk2 commented Jul 16, 2018

@ash73
Could you create a clean install of your operating system, then compile again and then compare the results ? If it isn’t the compiler, maybe it is some modification in the operating system that you are not aware of.

Gadgetoid commented Jul 17, 2018

@ash73 this time it has built successfully. The usleep error is a warning and not a fatal compilation error. Granted I’m not sure why it’s undeclared and I need to fix that, but the code should work.

If your C compiler is playing ball now you should run:

ash73 commented Jul 17, 2018

I tried again with a completely fresh install of Raspbian. This time it completed the setup but reported some warnings, see below.

Источник