install FILES given no DESTINATION! #132
Comments
|
@bookdude It looks like its dying when trying to call into python to get an install prefix. This is basically the underlying command, so it might be useful to figure out why its bombing on your system, I'm curious if it is also erroring out when run manually. anyway, the PYTHON3_INSTALL_DIR is empty because of the error and the configure is broken for that reason. Two work arounds if you cant reproduce and fix the error:
PS also check the PYTHONPATH and |
|
This didn't seem to do anything. ' /usr/bin/python3 -c "from distutils.sysconfig import get_python_lib; print(get_python_lib(plat_specific=True, prefix=''))" ' I'm not quite sure on where I should put this. |
@robman501a Are you able to clone and configure SoapySDR without this error (outside of pybombs, just git clone and mkdir build, cd build && cmake ../) I'm wondering if pybombs overloads the PYTHONPATH environment variable and causes python3 to crash. I don't think python3 is a big use case for pybombs apps, so maybe its ok to disable it in this case. Just a guess, but if cmake fails in pybombs and is ok without it, maybe thats the cause...
Its cmake arguments for SoapySDR project, so probably in the relevant pybomb file, I cant advice much more there. but I assume there is a place to add configuration args for cmake projects, since a lot of the pybombs apps are cmake based |
|
No issues building SoapySDR outside of PyBombs. rob@ubuntu:~/SoapySDR/build$ cmake ..
|
|
That probably means that pybombs is stomping on the PYTHONPATH. Im sure that pybombs is just setting the PYTHONPATH strategically to help it find gnuradio based python libs, and they just do not have to deal with python3 at all. In terms of being a package manager like homebrew, its probably not the best way to go. I'm genuinely curious what the PYTHONPATH is set to, if at all since it seems to be overriding system python packages, not just stuff in /usr/local. Still speculation, none of this is confirmed FWIW. So anyway, I can think of two things to resolve this:
|
|
Is there a way that I can still use pybombs install gr-gsm and just make it skip the SoapySDR part? |
|
'Find the maintainer of the soapysdr pybomb' I have no idea where to look or what to look form. |
|
I added an issue here: gnuradio/gr-recipes#91 |
|
Thanks. I wonder how the OP @bookdude is making out with this issue also. |
|
@oe3cts looks like this was your pybombs recipe file, any advice? |
|
Anyway, there is nothing I can do here, its a straightforward build issue. I opened bugs on the correct projects, reported the issue, made a suggestion to either fix the path or to modify the enable flags. Closing. thanks for reporting! |
Fails when installing as part of gr-gsm pybomb.
Installs without issue stand alone via clone \ cmake on the same system.
root@pi-gsm-01:~/git/SoapySDR/build# pybombs install gr-gsm
PyBOMBS - INFO - PyBOMBS Version 2.3.1
PyBOMBS.install_manager - INFO - Phase 1: Creating install tree and installing binary packages:
Install tree:
|
- gr-gsm
|
- gr-osmosdr
|
+- airspy
|
+- hackrf
|
- soapysdr
PyBOMBS.install_manager - INFO - Phase 2: Recursively installing source packages to prefix:
PyBOMBS.install_manager - INFO - Installing package: soapysdr
PyBOMBS.Packager.source - WARNING - Build dir already exists: /usr/local/src/soapysdr/build
Configuring: (100%) [======================================================================================================================================================================================================================]
PyBOMBS.Packager.source - WARNING - Configuration failed. Re-trying with higher verbosity.
-- #############################################
-- ## Begin configuration for Python support...
-- #############################################
-- Enabling optional Python bindings if possible...
-- SWIG_FOUND: TRUE - 2.0.12
-- PYTHONINTERP_FOUND: TRUE - 2.7.12
-- PYTHON_EXECUTABLE: /usr/bin/python
-- PYTHON_INSTALL_DIR: ${prefix}/lib/python2.7/dist-packages
-- PYTHONLIBS_FOUND: TRUE - 2.7.12
-- PYTHON_INCLUDE_DIRS: /usr/include/python2.7
-- PYTHON_LIBRARIES: /usr/lib/arm-linux-gnueabihf/libpython2.7.so
-- CMAKE_SWIG_FLAGS=-c++;-threads;-DSIZE_T_IS_UNSIGNED_INT
-- #############################################
-- ## Begin configuration for Python3 support...
-- #############################################
-- Enabling optional Python3 bindings if possible...
-- SWIG_FOUND: TRUE - 2.0.12
-- Could NOT find Python3InterpDbg (missing: PYTHON3_DBG_EXECUTABLE)
-- PYTHON3INTERP_FOUND: TRUE
-- PYTHON3_EXECUTABLE: /usr/bin/python3
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.5/distutils/sysconfig.py", line 14, in
import re
File "/usr/lib/python3.5/re.py", line 335, in
import copyreg
File "/usr/local/lib/python2.7/dist-packages/copyreg/init.py", line 7, in
raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3. Either you are trying to run from the python-future src folder or your installation of python-future is corrupted.
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 53, in apport_excepthook
if not enabled():
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 24, in enabled
import re
File "/usr/lib/python3.5/re.py", line 335, in
import copyreg
File "/usr/local/lib/python2.7/dist-packages/copyreg/init.py", line 7, in
raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3. Either you are trying to run from the python-future src folder or your installation of python-future is corrupted.
Original exception was:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.5/distutils/sysconfig.py", line 14, in
import re
File "/usr/lib/python3.5/re.py", line 335, in
import copyreg
File "/usr/local/lib/python2.7/dist-packages/copyreg/init.py", line 7, in
raise ImportError('This package should not be accessible on Python 3. '
ImportError: This package should not be accessible on Python 3. Either you are trying to run from the python-future src folder or your installation of python-future is corrupted.
-- PYTHON3_INSTALL_DIR: ${prefix}/
-- PYTHON3LIBS_FOUND: TRUE
-- PYTHON3_INCLUDE_DIRS: /usr/include/python3.5m
-- PYTHON3_LIBRARIES: /usr/lib/arm-linux-gnueabihf/libpython3.5m.so
-- CMAKE_SWIG_FLAGS=-c++;-threads;-DSIZE_T_IS_UNSIGNED_INT
CMake Error at python3/CMakeLists.txt:87 (install):
install TARGETS given no LIBRARY DESTINATION for module target
"_SoapySDR3".
CMake Error at python3/CMakeLists.txt:92 (install):
install FILES given no DESTINATION!
--
-- ######################################################
-- ## SoapySDR enabled features
-- ######################################################
-- ######################################################
-- ## SoapySDR disabled features
-- ######################################################
-- SoapySDR version: v0.6.1-g8c5db3e2
-- ABI/so version: v0.6
-- Install prefix: /usr/local
-- Configuring incomplete, errors occurred!
See also "/usr/local/src/soapysdr/build/CMakeFiles/CMakeOutput.log".
PyBOMBS.Packager.source - ERROR - Configuration failed after running at least twice.
PyBOMBS.Packager.source - ERROR - Problem occurred while building package soapysdr:
Configuration failed
PyBOMBS.install_manager - ERROR - Error installing package soapysdr. Aborting.
root@pi-gsm-01:~/git/SoapySDR/build#
The text was updated successfully, but these errors were encountered: