-
Notifications
You must be signed in to change notification settings - Fork 181
compilation error on ubuntu #73
Comments
This looks like a bug accidentally introduced in our cmake script. It currently doesn't handle specifying the python version in the python executable name. (e.g. It will take We've got a code push coming in the next couple weeks that should resolve it. In the meantime, the quickest work-around for you is likely to modify the
with:
|
thanks for fast answer, but i now get error in next step
|
This took some time to pin down. I think you're hitting bug related to using python 3.8. (So far, we've only tested up to python 3.6 ... and not on Ubuntu.) The script isn't able to determine the directory of the python shared object library and the name of that library no longer contains an "m". An actual fix is pending, but the work-around should be to manually add the location of that library. Modify the swig/PythonSetup.cmake to make this line: set(PYTHON_LIBRARIES "${PYTHON_PREFIX}/lib/libpython${PYTHON_VERSION_MAJOR}.${PYTHON_VERSION_MINOR}.so") look like this: set(PYTHON_LIBRARIES "/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so") Note: The actual library location may be different on your system. It looks like the best way to find that file is with the command: $ ls $(python3.8-config --configdir)/libpython3.8.so
# For me this yields:
/usr/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.so |
Also. I noticed you're using the command I'd suggest one or the other.
|
As of 9th April 2021 the error is back/still there in v.8.0.0 and the suggested workaround doesn't work as the number arguments expected doesn't match if the "3" is removed. |
Please show your modified command exactly as you executed it. Also, it would be helpful to know your system OS/environment configuration. |
Hello,
I try run compilation and get the error. (gpstk version 2.12 worked correctly on my old computer).
CMakeOutput.log
![Снимок экрана от 2020-11-10 22-03-19](https://user-images.githubusercontent.com/63191768/98691405-936bff00-23a0-11eb-82a3-fa09e1532613.png)
build.log
The text was updated successfully, but these errors were encountered: