Содержание
- MPI — error loading shared libraries
- 5 Answers 5
- PAX Terminal Setup
- B. Register configured terminal with host (Omaha only)
- C. Troubleshooting
- Bootup error: Terminal shows “PAXBASE.SO needs to update to Vx.xx” and/or “sxxapi01: needs to update to Vxxxxxx”; indicates that the terminal’s SO file needs update.
- RECEIVE ERROR displayed on terminal when processing transactions:
- NO ACTION TAKEN displayed on terminal when processing transactions:
- i. Terminal system password info
- ii. Terminal date and time info
- iii. Confirm terminal internet connection
- iv. Find terminal IP address and MAC address
- v. Manual batch close from terminal
- Linux python3 — Can’t open lib ‘SQL Server’
- 6 Answers 6
- OSError: libmtdev.so.1: cannot open shared object file: No such file or directory
- 2 Answers 2
- Ошибка error while loading shared libraries
- Что означает error while loading shared libraries?
- Как исправить ошибку?
- 1. Библиотека не установлена
- 2. Библиотека находится не в том каталоге
- 3. Неверная версия библиотеки
- Выводы
The problem I faced has been solved here: Loading shared library in open-mpi/ mpi-run
I know not how, setting LD_LIBRARY_PATH or specifying -x LD_LIBRARY_PATH fixes the problem, when my installation itself specifies the necessary -L arguments. My installation is in
I have also included my compile-link configs.
When I compiled with mpic++ and ran with mpirun a.out I got a (shared library) linker error
The error has been fixed by setting LD_LIBRARY_PATH . The question is how and why? What am i missing? Why is LD_LIBRARY_PATH required when my installation looks just fine.
5 Answers 5
libdl , libm , librt , libnsl and libutil are all essential system-wide libraries and they come as part of the very basic OS installation. libmpi and libmpi_cxx are part of the Open MPI installation and in your case are located in a non-standard location that must be explicitly included in the linker search path LD_LIBRARY_PATH .
It is possible to modify the configuration of the Open MPI compiler wrappers and make them pass the -rpath option to the linker. -rpath takes a library path and appends its to a list, stored inside the executable file, which tells the runtime link editor (a.k.a. the dynamic linker) where to search for libraries before it consults the LD_LIBRARY_PATH variable. For example, in your case the following option would suffice:
This would embed the path to the Open MPI libraries inside the executable and it would not matter if that path is part of LD_LIBRARY_PATH at run time or not.
To make the corresponding wrapper add that option to the list of compiler flags, you would have to modify the mpiXX-wrapper-data.txt file (where XX is cc , c++ , CC , f90 , etc.), located in mpi/share/openmpi/ . For example, to make mpicc pass the option, you would have to modify /home/vigneshwaren/mpi/share/openmpi/mpicc-wrapper-data.txt and add the following to the line that starts with linker_flags= :
$ is automatically expanded by the wrapper to the current Open MPI installation path.
Источник
PAX Terminal Setup
Before you can perform an App Update, the terminal must be configured with an application and parameters through BroadPOS. Once the terminal is fully configured, BroadPOS will indicate “Waiting for download” as the terminal’s Deployment status on the My Terminals page; if there is any other status indicated, than the terminal has already “Completed” download of its most recent application or it still requires further configuring.
Press the ‘FUNC’ key (input password; see appendix i for more info on system passwords).
Navigate to: System Settings->App Management.
Select ‘App Update’.
Note: during the App Update download process, the terminal may sporadically prompt, “APP UPDATE, Failed to DownLD, AGAIN? (ENTR=YES)”. Pressing ‘ENTER’ ought to resume the download at the same percentage that it stopped.
If the download continues to fail, there is likely a connection issue; see appendix iii .
B. Register configured terminal with host (Omaha only)
Once the processor application has been configured and successfully downloaded to the terminal, you’ll need to register the terminal with the host before transactions can be processed.
Press the ‘FUNC’ key (input password).
Navigate to: Hosts Settings->Hosts Parameters->Host Register.
Note: if the terminal returns an error, i.e. “STATUS ERROR (Au”, then you need to contact the FirstData Datawire to have the account reset.
C. Troubleshooting
Bootup error: Terminal shows “PAXBASE.SO needs to update to Vx.xx” and/or “sxxapi01: needs to update to Vxxxxxx”; indicates that the terminal’s SO file needs update.
Power cycle the terminal.
During the SELF-TEST, press the ‘FUNC’ key, then press ‘CANCEL’.
Select ‘New Download’.
Select TCP as the Communication Method
Input «50.79.90.190» as the remote IP.
Input «8001» for the port number.
Input the terminal ID as “80000001”.
Select ‘Yes’ if «Auto get local IP address(DHCP)» is prompted.
RECEIVE ERROR displayed on terminal when processing transactions:
This indicates that one or more of the host/merchant parameters are incorrect, in which case the host immediately shuts down the communication, which results in the terminal timing out after a delay. Double check that all BroadPOS parameters match what’s on the VAR sheet. If problem persists, contact host.
NO ACTION TAKEN displayed on terminal when processing transactions:
This indicates that the card issuer rejected the particular transaction, possibly because they don’t support the transaction type; retrying the transaction won’t resolve the issue. Merchants can have the user try a different card and contact their host for more details.
i. Terminal system password info
Default system password for PAX terminals is the current date in the mmddyyyy format (eg. 04272016), meaning the password changes every day. The system password can also be re-configured through BroadPOS.
ii. Terminal date and time info
It is essential that the terminal’s system date/time is correct. The terminal will trigger auto-batches based on its system date/time, NOT the local time or configured timezone; so if the system date/time is not the same as the merchant’s local time, it will cause confusion because batches will close at a time different than the terminal’s BroadPOS-configured Start Batch Time and End Batch Time.
Set system date/time :
Press the ‘FUNC’ key (input password).
Navigate to: System Settings->Date/Time Setup.
On the screen that displays the system’s current date/time, input the actual current date (MM/DD/YYYY), followed by the actual current time (24 hour format), and then press ‘ENTER’.
iii. Confirm terminal internet connection
Press the ‘FUNC’ key (input password).
Navigate to: Communication->LAN Parameters->PING
Press ‘ENTER’ key to ping WWW.GOOGLE.COM
Terminal will indicate PING OK or PING FAILED; if failed, then there are connectivity issues between the terminal and the internet that need to be resolved before the processor application and parameters can be updated or any transactions can be processed.
iv. Find terminal IP address and MAC address
These are often needed for reserving the terminals’ IP on the network; this is essential to the POS system which sends transaction requests to the terminal based on the IP.
Press the ‘FUNC’ key (input password).
Navigate to: Communication->LAN Parameters
Select ‘IP Address’ or ‘MAC Address’ to view the terminal’s current addresses.
v. Manual batch close from terminal
The majority of merchants ought to be configured through BroadPOS to auto-batch, but there are scenarios where the merchant may have to manually batch close (for instance, the Batch Start/End Times weren’t set or the system Date/Time was incorrect).
Press the ‘FUNC’ key (input password).
Navigate to: Hosts Settings->Batch Close->Batch All
Press the ‘ENTER’ key on the following Batch All totals screen.
Источник
Linux python3 — Can’t open lib ‘SQL Server’
I am trying to connect to an Microsoft Azure SQL server database.
This is how i am trying to connect:
I am getting an error while excuting this line. The error:
Can’t figure why this is happening, Any idea?
6 Answers 6
Update — December 2022
The current installation instructions for the ODBC driver are here
I also recommend you install the ODBC Driver and then try to use pyodbc. I am assuming you are on an Ubuntu 15.04+ machine.
To install the ODBC Driver follow the following instructions:
Once you do that, install pyodbc using pip and try the following script:
Let me know how that goes.
Download Dependencies depends on your platform, (for other OS Download your Dependencies)
This example for Ubuntu:
and then change,
Check those links. It solved my problems which were kind of similar.
I see that this post has an accepted answer but it did not work for me running Python 3.8 on Ubuntu 20.04. I tried several things but I think that ultimately, it was a security issue having to do with the openSSL package. Here are the steps I recommend.
Check the openSSL version. Do this in the Linux console
The problematic version was 1.1.1f on my system. If that is the version you have, update it with these commands
Then you have to edit /etc/ssl/openssl.cnf . Put this in the beginning
And this at the end
Like I said, that worked for me. Hopefully it can help someone else too.
Источник
Somebody know how I can fix this error. In google search incredibly old information, i don’t found answer. When i close my app, my x-server on Linux start work unbelievably bad. Do not work normal OpenGL 2.0 and OpenGL 3.1, working only XRender without VSync on my KDE neon last version.
2 Answers 2
I had same issue on Linux Mint 20.2 Cinnamon, but may be similar for other Linux distributions, like Ubuntu.
It was because I installed PyCharm Community Edition using «Software Manager». It seems ok at very first step, but because it is delivered as flatpack it is not able to access and cooperate with host Linux resources properly. For example you cannot access Python installed on your machine, you cannot load shared libraries from your machine. That’s root cause with MTDev and libmtdev.so.1 false unavaibility. I also was not able to launch projects outside od PyCharm, because Python venv points to Python binaries which exists only in PyCharm app virtualized environment.
If you are using PyCharm installed by «Software Manager», uninstall it, then download it from official url:
Unpack downloaded file into folder you like, then start bin/pycharm.sh everytime you want to launch PyCharm.
PyCharm will launch faster, and you will have no issues with loading shared libraries for MTDev.
Of course if MTDev is not present on your machine, then you have to install it too:
Источник
Новые и опытные пользователи Linux могут сталкиваться с ошибкой error loading shared libraries во время запуска программ, также с ней могут сталкиваться программисты и все желающие компилировать программное обеспечение в своей системе. Эта ошибка в дословном переводе означает что возникла проблема во время загрузки общей библиотеки. О том что такое библиотеки и зачем они нужны вы можете узнать из статьи библиотеки Linux.
В этой же статье мы рассмотрим что значит ошибка error while loading shared libraries более подробно, а главное, как ее решить.
Даже если вы не компилируете свои программы, то вы можете увидеть ошибку error while loading shared libraries: имя_библиотеки: cannot open shared object file: No such file or directory достаточно часто во время установки новых программ не через пакетный менеджер или программ, предназначенных для другого дистрибутива. Как я уже говорил, она возникает потому, что система не может найти библиотеку.
А вот почему ее нельзя найти и загрузить, это уже интересно. Этому может быть несколько причин:
- Библиотека не установлена в системе;
- Библиотека установлена, но неизвестно куда;
- Библиотека установлена правильно, но имеет не ту версию.
При решении проблемы мы будем руководствоваться именно этими причинами и пытаться их решить.
Как исправить ошибку?
1. Библиотека не установлена
Первый вариант, тут все понятно, библиотеки просто нет в системе, поэтому мы и получаем такую ошибку. Верный способ ее решения — просто найти пакет библиотеки с помощью пакетного менеджера и установить ее. Обычно, пакеты с библиотеками называются так же, как и сами библиотеки с префиксом lib.
Например, если нам не хватает библиотеки libfuse2.so, то мы можем найти ее в Ubuntu такой командой:
sudo apt search libfuse2
Затем осталось только установить ее:
sudo apt install libfuse2
Если перед вами стоит задача собрать программу из исходников, то вам понадобится не только установить саму библиотеку, но и заголовочные файлы для нее:
sudo apt install libfuse-dev
И так для любой библиотеки. Но это не всегда помогает.
2. Библиотека находится не в том каталоге
Бывает что библиотека установлена, мы установили ее или она поставлялась вместе с программой, но ошибка как была, так и есть. Причиной этому может быть то, что загрузчик Linux не может найти библиотеку.
Поиск библиотек выполняется по всех папках, которые указаны в конфигурационных файлах /etc/ld.conf.d/. По умолчанию, это такие каталоги, как /usr/lib, /lib, /usr/lib64, /lib64. Если библиотека установлена в другой каталог, то, возможно, это и есть причина проблемы.
Вы можете посмотреть какие библиотеки сейчас доступны загрузчику с помощью команды:
Найти, где находится ваша библиотека можно с помощью команды locate. Например, нас интересует библиотека librtfreader.so:
Теперь мы знаем, что она находится по адресу /opt/kingsoft/wps-office/office6/. А значит, для работы программы необходимо сделать чтобы загрузчик библиотек ее видел. Для этого можно добавить путь в один из файлов /etc/ld.so.conf.d/ или же в переменную LD_LIBRARY_PATH:
Опять же, так вы можете поставить с любой библиотекой, которая взывает ошибку. Еще один более простой метод — это просто создать символическую ссылку на нужную библиотеку в правильной папке:
ln -s /opt/kingsoft/wps-office/office6/librtfreader.so /usr/lib/librtfreader.so
3. Неверная версия библиотеки
Эта причина ошибки довольно часто встречается при использовании программ не для вашего дистрибутива. Каждая библиотека имеет дополнительную версию, так называемую ревизию, которая записывается после расширения .so. Например, libav.so.1. Так вот, номер версии меняется всякий раз, когда в библиотеку вносятся какие-либо исправления.
Часто возникает ситуация, когда в одном дистрибутиве программа собирается с зависимостью от библиотеки, например, libc.so.1, а в другом есть только libc.so.2. Отличия в большинстве случаев здесь небольшие и программа могла бы работать на второй версии библиотеки. Поэтому мы можем просто создать символическую ссылку на нее.
Например, библиотеки libusb-1.0.so.1 нет. Но зато есть libusb-1.0.so.0.1, и мы можем ее использовать:
Для этого просто создаем символическую ссылку на библиотеку:
sudo ln -s /usr/lib/libusb-1.0.so.0.1 /usr/lib/libusb-1.0.so.1
В большинстве случаев программа не заметит подмены и будет работать, как и ожидалось. Также для решения этой проблемы можно попытаться найти нужную версию библиотеки в интернете для своей архитектуры и поместить ее в папку /usr/lib/ или /usr/lib64/. Но после этого желательно обновить кэш:
Выводы
В этой статье мы рассмотрели почему возникает ошибка Error while loading shared libraries, а также как ее решить. В большинстве случаев проблема решается довольно просто и вы получите работоспособную программу. Надеюсь, эта информация была полезной для вас.
Источник
I’m trying to run a game (PRIME, an old Rougelike found here) and after downloading the 64 bit linux version, and going to run it, I get this error response:
./prime: error while loading shared libraries: libsigsegv.so.2: cannot
open shared object file: No such file or directory
Now, I’ve checked that I’ve got that file in my library, and it’s up to date. The last time I asked this question I was able to solve it simply with a sudo-apt-update, sudo-apt-upgrade. That isn’t working this time.
(The italicized note above is technically a mistake. I did have that file, but not the i386 version. Take a look at the accepted answer and my comments to see how we discovered that!)
My real item is this, though: Shared library problems are a pretty common error, it seems, and although the library in question changes, the other common issue is that the library exists, but for some reason the executable (or the user?) can’t find it?
This is also not the first time I’ve had this issue on this system.
Is there a general solution or approach to shared library problems?
I came across this using ldconfig but I haven’t been able to get it to work.
output of ldd ./prime in the directory with that executable
linux-gate.so.1 (0xf7f03000)
libsigsegv.so.2 => not found
libnoteye.so => ./libnoteye.so (0xf7e4f000)
libncurses.so.5 => /lib/i386-linux-gnu/libncurses.so.5 (0xf7e26000)
libtinfo.so.5 => /lib/i386-linux-gnu/libtinfo.so.5 (0xf7e00000)
libpanel.so.5 => /usr/lib/i386-linux-gnu/libpanel.so.5 (0xf7df9000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7c1b000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf7b16000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf7af7000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf7908000)
libSDL-1.2.so.0 => not found
libSDL_image-1.2.so.0 => not found
liblua5.1.so.0 => not found
libutil.so.1 => /lib/i386-linux-gnu/libutil.so.1 (0xf7901000)
libSDL_mixer-1.2.so.0 => not found
libSDL_net-1.2.so.0 => not found
libGL.so.1 => /usr/lib/i386-linux-gnu/libGL.so.1 (0xf7894000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf7876000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7870000)
/lib/ld-linux.so.2 (0xf7f04000)
libGLdispatch.so.0 => /usr/lib/i386-linux-gnu/libGLdispatch.so.0 (0xf77f3000)
libGLX.so.0 => /usr/lib/i386-linux-gnu/libGLX.so.0 (0xf77b7000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf7666000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf7637000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf7631000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf7629000)
libbsd.so.0 => /usr/lib/i386-linux-gnu/libbsd.so.0 (0xf760a000)
#1 2008-09-21 13:52:57
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
[SOLVED]Error opening PCM device hw:0,0
I am trying to use Jesusonic, but I get the following error:
mmanu > Desktop/jesusonic-0.991-linux-x86/jesusonic -mode ALSA -nbufs 2
Jesusonic v0.991 - Copyright (C) 2004-2005 Cockos Incorporated
Using output mode: 'ALSA'
Opening ALSA 'hw:0,0' for read
Opening ALSA 'hw:0,0' for write
Error opening PCM device hw:0,0My audio card is an integrated Intel one:
Audio device: Intel Corporation module: snd-hda-intel
82801G (ICH7 Family) High Definition Audio ControllerI am not very expert with audio devices and functionality, so is there anything I can look up or do to solve this problem?
Thank you for your time 
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#2 2008-09-21 14:34:00
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
What’s the output of cat /proc/asound/cards?
#3 2008-09-21 14:46:29
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Here you go:
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf0580000 irq 16Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#4 2008-09-21 15:41:58
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
Hi again finferflu,
I downloaded the software and it’s working here, so bare with me while I guess (which I am doing). What about cat /proc/asound/devices?
#5 2008-09-21 15:49:39
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Thanks, skottish, for your effort
Here you go:
2: : timer
3: : sequencer
4: [ 0- 1]: digital audio playback
5: [ 0- 0]: digital audio playback
6: [ 0- 0]: digital audio capture
7: [ 0- 0]: hardware dependent
8: [ 0] : controlHave you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#6 2008-09-21 16:06:22
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
My lack of understanding is really showing here…
The default format for alsa is implicitly defined like this:
jesusonic -mode ALSA -in hw:0,0 -out hw:0,0
I’m posting this in the hope that someone that knows hardware will be able to tell you how to identify the proper address. Of course another (very hackish) solution is to just try some other value like hw:0,1 on both. 0,0 and 0,1 work on my machine, but it fails with the same error you have on 0,2.
Last edited by skottish (2008-09-21 16:17:33)
#7 2008-09-21 20:34:01
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Thanks, skottish!
jesusonic -mode ALSA -nbuff 2 -in hw:0,0 -out hw:0,1Was the way to go.
Now I just wonder: do you also get an empty effects menu? Last time I have used Jesusonic it was full of effects… I might be missing some other download perhaps…
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#8 2008-09-21 20:52:31
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
When I get to the first screen, it says «No effects active — hit A to add an effect». When I hit ‘a’, I get a list of effects: Delay, Guitar, Meters,… Is this what you’re missing?
Last edited by skottish (2008-09-21 20:54:48)
#9 2008-09-21 20:54:10
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Yes, that’s what I’m missing, I don’t see any list.
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#10 2008-09-21 20:55:53
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
finferflu wrote:
Yes, that’s what I’m missing, I don’t see any list.
I’m sort of stuck how much farther I can help. If I add anything to the list I get a segfault. It’s probably because I’m missing something; I’m on 64 bit and got lucky with the 32 bit libraries that I have.
#11 2008-09-21 21:01:42
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
I’m on a 32bit, but the app is recommended for usage on a 64bit machine (I know it works on 32bit because I have used it in the past on my previous 32bit machine).
EDIT:
Found out: my working directory wasn’t the one containing the jesusonic executable, so I guess the app follows a relative path. That’s it!
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
#12 2008-09-21 21:16:09
- skottish
- Forum Fellow
- From: Here
- Registered: 2006-06-16
- Posts: 7,942
Re: [SOLVED]Error opening PCM device hw:0,0
The download that I found is without a doubt 32 bit. It’s the only one I found. Although, they do reference a 64 bit version of Reaper on the page which includes Jesusonic.
#13 2008-09-21 22:05:13
- finferflu
- Forum Fellow
- From: Manchester, UK
- Registered: 2007-06-21
- Posts: 1,899
- Website
Re: [SOLVED]Error opening PCM device hw:0,0
Ok, I must have misread it…
Anyway, I found where the error was actually lying: Firefox was apparently using the playback device, so it was busy. Stupid me, not thinking about it before.
Have you Syued today?
Free music for free people! | Earthlings
«Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.» — A. de Saint-Exupery
I am trying to install tensorflow-1.14.0-cp27-none-linux_aarch64.whl on a development board.
Development board has Debian, Release 10 installed.
Python 2.7
I had installed the dependences.
Did anyone encounter this issue too? Thanks!
After executing «pip install —user tensorflow-1.14.0-cp27-none-linux_aarch64.whl», I got following error:
Processing ./tensorflow-1.14.0-cp27-none-linux_aarch64.whl
Collecting keras-preprocessing>=1.0.5 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/28/6a/8c1f62c37212d9fc441a7e26736df51ce6f0e38455816445471f10da4f0a/Keras_Preprocessing-1.1.0-py2.py3-none-any.whl
Collecting enum34>=1.1.6 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/c5/db/e56e6b4bbac7c4a06de1c50de6fe1ef3810018ae11732a50f15f62c7d050/enum34-1.1.6-py2-none-any.whl
Collecting keras-applications>=1.0.6 (from tensorflow==1.14.0)
Requirement already satisfied: six>=1.10.0 in /usr/lib/python2.7/dist-packages (from tensorflow==1.14.0) (1.12.0)
Collecting grpcio>=1.8.6 (from tensorflow==1.14.0)
Requirement already satisfied: numpy<2.0,>=1.14.5 in /usr/lib/python2.7/dist-packages (from tensorflow==1.14.0) (1.16.2)
Collecting tensorboard<1.15.0,>=1.14.0 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/f4/37/e6a7af1c92c5b68fb427f853b06164b56ea92126bcfd87784334ec5e4d42/tensorboard-1.14.0-py2-none-any.whl
Collecting gast>=0.2.0 (from tensorflow==1.14.0)
Collecting google-pasta>=0.1.6 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/35/95/d41cd87d147742ef72d5d1dc317318486e3fbffdadf24a60e70dedf01d56/google_pasta-0.1.7-py2-none-any.whl
Collecting protobuf>=3.6.1 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/0d/2e/d4b1b67c264ce6722def110f2715461e9b4d49647952750c82c6b247bfa6/protobuf-3.9.1-py2.py3-none-any.whl
Collecting tensorflow-estimator<1.15.0rc0,>=1.14.0rc0 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/3c/d5/21860a5b11caf0678fbc8319341b0ae21a07156911132e0e71bffed0510d/tensorflow_estimator-1.14.0-py2.py3-none-any.whl
Collecting backports.weakref>=1.0rc1 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/88/ec/f598b633c3d5ffe267aaada57d961c94fdfa183c5c3ebda2b6d151943db6/backports.weakref-1.0.post1-py2.py3-none-any.whl
Collecting absl-py>=0.7.0 (from tensorflow==1.14.0)
Requirement already satisfied: wheel in /usr/lib/python2.7/dist-packages (from tensorflow==1.14.0) (0.32.3)
Collecting wrapt>=1.11.1 (from tensorflow==1.14.0)
Requirement already satisfied: mock>=2.0.0 in /usr/lib/python2.7/dist-packages (from tensorflow==1.14.0) (2.0.0)
Collecting termcolor>=1.1.0 (from tensorflow==1.14.0)
Collecting astor>=0.6.0 (from tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/d1/4f/950dfae467b384fc96bc6469de25d832534f6b4441033c39f914efd13418/astor-0.8.0-py2.py3-none-any.whl
Collecting h5py (from keras-applications>=1.0.6->tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/5f/97/a58afbcf40e8abecededd9512978b4e4915374e5b80049af082f49cebe9a/h5py-2.10.0.tar.gz
Collecting futures>=2.2.0; python_version < «3.2» (from grpcio>=1.8.6->tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/d8/a6/f46ae3f1da0cd4361c344888f59ec2f5785e69c872e175a748ef6071cdb5/futures-3.3.0-py2-none-any.whl
Collecting markdown>=2.6.8 (from tensorboard<1.15.0,>=1.14.0->tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/c0/4e/fd492e91abdc2d2fcb70ef453064d980688762079397f779758e055f6575/Markdown-3.1.1-py2.py3-none-any.whl
Collecting werkzeug>=0.11.15 (from tensorboard<1.15.0,>=1.14.0->tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/ce/42/3aeda98f96e85fd26180534d36570e4d18108d62ae36f87694b476b83d6f/Werkzeug-0.16.0-py2.py3-none-any.whl
Collecting setuptools>=41.0.0 (from tensorboard<1.15.0,>=1.14.0->tensorflow==1.14.0)
Using cached https://files.pythonhosted.org/packages/b2/86/095d2f7829badc207c893dd4ac767e871f6cd547145df797ea26baea4e2e/setuptools-41.2.0-py2.py3-none-any.whl
Building wheels for collected packages: h5py
Building wheel for h5py (setup.py) … error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python -u -c ‘import sys, setuptools, tokenize; sys.argv[0] = ‘»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘; file='»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘;f=getattr(tokenize, ‘»‘»‘open'»‘»‘, open)(file);code=f.read().replace(‘»‘»‘rn'»‘»‘, ‘»‘»‘n'»‘»‘);f.close();exec(compile(code, file, ‘»‘»‘exec'»‘»‘))’ bdist_wheel -d /tmp/pip-wheel-2H1BW_ —python-tag cp27
cwd: /tmp/pip-install-rPQoSI/h5py/
Complete output (88 lines):
Unable to find pgen, not compiling formal grammar.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Plex/Scanners.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Plex/Actions.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/Scanning.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/Visitor.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/FlowControl.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Runtime/refnanny.pyx because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/FusedNode.py because it changed.
Compiling /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Tempita/_tempita.py because it changed.
[1/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/FlowControl.py
[2/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/FusedNode.py
[3/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/Scanning.py
[4/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Compiler/Visitor.py
[5/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Plex/Actions.py
[6/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Plex/Scanners.py
[7/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Runtime/refnanny.pyx
[8/8] Cythonizing /tmp/easy_install-92LcTy/Cython-0.29.13/Cython/Tempita/_tempita.py
warning: no files found matching ‘Doc/‘
warning: no files found matching ‘.pyx’ under directory ‘Cython/Debugger/Tests’
warning: no files found matching ‘.pxd’ under directory ‘Cython/Debugger/Tests’
warning: no files found matching ‘.pxd’ under directory ‘Cython/Utility’
warning: no files found matching ‘pyximport/README’
Installed /tmp/pip-install-rPQoSI/h5py/.eggs/Cython-0.29.13-py2.7-linux-aarch64.egg
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-aarch64-2.7
creating build/lib.linux-aarch64-2.7/h5py
copying h5py/highlevel.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/h5py_warnings.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/ipy_completer.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/init.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/version.py -> build/lib.linux-aarch64-2.7/h5py
creating build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/group.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/attrs.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/datatype.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/compat.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/init.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/files.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/selections.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/base.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/dims.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/dataset.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/vds.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/selections2.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/filters.py -> build/lib.linux-aarch64-2.7/h5py/_hl
creating build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_completions.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attribute_create.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_threads.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file_image.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file2.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_base.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dimension_scales.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset_swmr.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5d_direct_chunk.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_group.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_slicing.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_deprecation.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5f.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attrs_data.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/init.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dtype.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset_getitem.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_selections.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dims_dimensionproxy.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5p.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_filters.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attrs.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/common.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_datatype.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5pl.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_objects.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5t.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file.py -> build/lib.linux-aarch64-2.7/h5py/tests
creating build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/init.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_lowlevel_vds.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_highlevel_vds.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_virtual_source.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
running build_ext
(‘Loading library to get version:’, ‘libhdf5.so’)
error: libhdf5.so: cannot open shared object file: No such file or directory
ERROR: Failed building wheel for h5py
Running setup.py clean for h5py
Failed to build h5py
Installing collected packages: keras-preprocessing, enum34, h5py, keras-applications, futures, grpcio, setuptools, markdown, werkzeug, absl-py, protobuf, tensorboard, gast, google-pasta, tensorflow-estimator, backports.weakref, wrapt, termcolor, astor, tensorflow
Found existing installation: Keras-Preprocessing 1.0.3
Uninstalling Keras-Preprocessing-1.0.3:
Successfully uninstalled Keras-Preprocessing-1.0.3
Running setup.py install for h5py … error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python -u -c ‘import sys, setuptools, tokenize; sys.argv[0] = ‘»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘; file='»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘;f=getattr(tokenize, ‘»‘»‘open'»‘»‘, open)(file);code=f.read().replace(‘»‘»‘rn'»‘»‘, ‘»‘»‘n'»‘»‘);f.close();exec(compile(code, file, ‘»‘»‘exec'»‘»‘))’ install —record /tmp/pip-record-lEbOfd/install-record.txt —single-version-externally-managed —compile —user —prefix=
cwd: /tmp/pip-install-rPQoSI/h5py/
Complete output (64 lines):
running install
running build
running build_py
creating build
creating build/lib.linux-aarch64-2.7
creating build/lib.linux-aarch64-2.7/h5py
copying h5py/highlevel.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/h5py_warnings.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/ipy_completer.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/init.py -> build/lib.linux-aarch64-2.7/h5py
copying h5py/version.py -> build/lib.linux-aarch64-2.7/h5py
creating build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/group.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/attrs.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/datatype.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/compat.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/init.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/files.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/selections.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/base.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/dims.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/dataset.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/vds.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/selections2.py -> build/lib.linux-aarch64-2.7/h5py/_hl
copying h5py/_hl/filters.py -> build/lib.linux-aarch64-2.7/h5py/_hl
creating build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_completions.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attribute_create.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_threads.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file_image.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file2.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_base.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dimension_scales.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset_swmr.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5d_direct_chunk.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_group.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_slicing.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_deprecation.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5f.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attrs_data.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/init.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dtype.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset_getitem.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_selections.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dims_dimensionproxy.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5p.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_filters.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_dataset.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_attrs.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/common.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_datatype.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5pl.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_objects.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_h5t.py -> build/lib.linux-aarch64-2.7/h5py/tests
copying h5py/tests/test_file.py -> build/lib.linux-aarch64-2.7/h5py/tests
creating build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/init.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_lowlevel_vds.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_highlevel_vds.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
copying h5py/tests/test_vds/test_virtual_source.py -> build/lib.linux-aarch64-2.7/h5py/tests/test_vds
running build_ext
(‘Loading library to get version:’, ‘libhdf5.so’)
error: libhdf5.so: cannot open shared object file: No such file or directory
—————————————-
ERROR: Command errored out with exit status 1: /usr/bin/python -u -c ‘import sys, setuptools, tokenize; sys.argv[0] = ‘»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘; file='»‘»‘/tmp/pip-install-rPQoSI/h5py/setup.py'»‘»‘;f=getattr(tokenize, ‘»‘»‘open'»‘»‘, open)(file);code=f.read().replace(‘»‘»‘rn'»‘»‘, ‘»‘»‘n'»‘»‘);f.close();exec(compile(code, file, ‘»‘»‘exec'»‘»‘))’ install —record /tmp/pip-record-lEbOfd/install-record.txt —single-version-externally-managed —compile —user —prefix= Check the logs for full command output.