Error during installation: libyade.so
Hello everyone,
When I was trying to install yade_2018.02b from source code on Ubuntu 16.04 (64bit).
I have successfully finished the "cmake" without errors and the enabled and disabled options were shown as:
-- =======
-- Yade configured with following features: Odeint VTK OpenMP GTS GUI-Qt5 CGAL PFVFLOW TWOPHASEFLOW LINSOLV SPH DEFORM LIQMIGRATION GL2PS LBMFLOW MASK_ARBITRARY PROFILING PotentialParticles PotentialBlocks
-- Disabled features: CHOLMOD_GPU
-- Optimized build
-- =======
-- Configuring done
-- Generating done
-- Build files have been written to: /home/yufan/
However, there is something wrong during the subsequent "make" step.
The log with errors:
root@yufan-
[ 1%] Automatic moc for target boot
[ 2%] Automatic moc for target yade
[ 2%] Built target boot_automoc
[ 2%] Automatic moc for target _GLViewer
[ 2%] Built target _GLViewer_automoc
[ 3%] Automatic moc for target _polyhedra_utils
[ 3%] Built target _polyhedra_
[ 3%] Built target yade_automoc
[ 3%] Automatic moc for target _packSpheres
[ 3%] Automatic moc for target _packPredicates
[ 3%] Built target _packSpheres_
[ 3%] Built target _packPredicates
[ 4%] Automatic moc for target wrapper
[ 4%] Automatic moc for target _packObb
[ 4%] Built target wrapper_automoc
[ 4%] Built target _packObb_automoc
[ 4%] Automatic moc for target WeightedAverage2d
[ 5%] Automatic moc for target _utils
[ 5%] Built target WeightedAverage
[ 5%] Built target _utils_automoc
[ 5%] Automatic moc for target _customConverters
[ 5%] Built target _customConverte
[ 6%] Built target _polyhedra_utils
[ 10%] Built target _GLViewer
[ 12%] Built target _packObb
[ 13%] Built target WeightedAverage2d
[ 13%] Linking CXX shared library lib/x86_
/usr/bin/ld: /usr/local/
/usr/local/
collect2: error: ld returned 1 exit status
CMakeFiles/
make[2]: *** [lib/x86_
CMakeFiles/
make[1]: *** [CMakeFiles/
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
I will be appreciate if someone can give me some tips to solve the problem.
Thanks very much.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Yade Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- YUFAN ZHAO
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Did you try to "recompile with -fPIC" ?
Revision history for this message
|
#2 |
@Robert:
> SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -O2 --param=
this is from CMakeLists.txt of 2018.02b, -fPIC should be already there
@yufan: what does "make VERBOSE=ON" tells?
Jan
Revision history for this message
|
#3 |
Also try compiling without "sudo".
Revision history for this message
|
#4 |
@Robert
>Also try compiling without "sudo".
Thanks for your advice, but it made no sense w/ or w/o "sudo".
Revision history for this message
|
#5 |
@Jan
>what does "make VERBOSE=ON" tells?
Thanks for your reply. There was no change about the error after typing "make VERBOSE=ON".
The log shown as below:
[ 6%] Linking CXX shared library lib/x86_
/usr/bin/cmake -E cmake_link_script CMakeFiles/
/usr/bin/c++ -fPIC -fPIC -O2 --param=
/usr/bin/ld: /usr/local/
/usr/local/
collect2: error: ld returned 1 exit status
CMakeFiles/
make[2]: *** [lib/x86_
make[2]: Leaving directory '/home/
CMakeFiles/
make[1]: *** [CMakeFiles/
make[1]: Leaving directory '/home/
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
Could you help me to point out the problem and give any advice?
Thank you in advance!
Revision history for this message
|
#6 |
> There was no change about the error after typing "make VERBOSE=ON".
>
> /usr/bin/c++ -fPIC ...
the point was that now it is clear that -fPIC was used
why you want to build Yade 2018.02b from source?
A solution **could** be to use a newer version of Ubuntu (with no guarantee of success and all the disadvantages of system upgraging).
cheers
Jan
Revision history for this message
|
#7 |
Hi, please try to build again in a new folder and show the output of cmake this time.
Bruno
Revision history for this message
|
#8 |
@Jan
Thank you very much.
>A solution **could** be to use a newer version of Ubuntu (with no guarantee of success and all the disadvantages of system upgrading).
Actually, I tried to install 2019 at first, but I encountered the problem that I described above. Then I turned to a different version (2018.02b) and the same problem occurred.
Revision history for this message
|
#9 |
@Bruno
>please try to build again in a new folder and show the output of cmake this time.
Thanks very much for your response. I built again into another folder and the info. is shown as below:
root@yufan-
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_
-- Performing Test OpenMP_
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_
-- Performing Test OpenMP_
-- Found OpenMP: -fopenmp
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake (found version "4.8.7")
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Version is set to 2019.01a
-- Found OpenGL: /usr/lib/
-- GTS using gts-config /usr/bin/gts-config
-- Using GTS from /usr
-- Found GL2PS: /usr/lib/
-- Found CGAL: /usr/include, /usr/lib/
-- Found NumPy: version "1.11.0" /usr/lib/
-- Found Loki: /usr/include
-- GCC Version >= 4.8. Adding -ftrack-
-- GCC Version >= 4.8. Adding -save-temps
-- GCC Version >= 4.9. Adding -fstack-
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.58.0
-- Found the following Boost libraries:
-- python
-- thread
-- filesystem
-- iostreams
-- regex
-- serialization
-- system
-- date_time
-- chrono
-- atomic
-- Boost_VERSION: 105800
-- Boost_LIB_VERSION: 1_58
-- Boost_INCLUDE_DIRS: /usr/include
-- Boost_LIBRARIES: /usr/lib/
-- Found Eigen3: /usr/include/eigen3 (Required is at least version "2.91.0")
-- Found BZip2: /usr/local/
-- Looking for BZ2_bzCompressInit
-- Looking for BZ2_bzCompressInit - found
-- Found ZLIB: /usr/lib/
-- Found PythonLibs: /usr/lib/
-- Found Eigen3, version: 3.2.92
-- Disable vectorization
-- The imported target "vtkRenderingPy
"/usr/
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/
but not all the files it references.
-- The imported target "vtk" references the file
"/usr/bin/vtk"
but this file does not exist. Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
"/usr/
but not all the files it references.
-- Found VTK
-- Found OpenMP
-- GTS using gts-config /usr/bin/gts-config
-- Using GTS from /usr
-- Checking for one of the modules 'glib-2.0'
-- Found GLib2: glib-2.0 /usr/include/
-- Looking for include file glib/gregex.h
-- Looking for include file glib/gregex.h - not found
-- Found GTS
-- Found GLUT: /usr/lib/
-- USE QT5
-- Found QGLVIEWER-qt5: /usr/include/
-- Found GUI-Qt5-LIBS
-- GMP libs: /usr/lib/
-- Found GMP: /usr/include/
-- GMP libs: /usr/lib/
-- Found CGAL
-- SuiteSparse version 4.4.6 found, CHOLMOD direct solver for CPU activated.
-- Found Cholmod: /usr/lib/
-- Found OpenBlas: /usr/lib/
-- Found Metis: /usr/include
-- Found Cholmod in /usr/lib/
-- Found OpenBlas in /usr/lib/
-- Found Metis in /usr/lib/
-- Could NOT find CuBlas (missing: CUBLAS_LIBRARY CUDART_LIBRARY)
-- Found Lapack: /usr/lib/
-- Missing dependency for CHOLMOD_GPU, disabled
-- Found GL2PS
LBMFLOW is still experimental, building and running LBM engine are at your own risk!
MASK_ARBITRARY_SIZE = 256
-- Looking for sgemm_
-- Looking for sgemm_ - found
-- A library with BLAS API found.
-- Looking for cheev_
-- Looking for cheev_ - found
-- A library with LAPACK API found.
-- Found OpenBlas
-- Found Lapack
-- Found CLP: /usr/include/coin, /usr/lib/
-- A library with BLAS API found.
-- A library with LAPACK API found.
-- Found CLP
Yade will be installed to /home/yufan/
-- Suffix is set to -2019.01a
-- LIBRARY_OUTPUT_PATH is set to lib/x86_
-- runtimePREFIX is set to /home/yufan/
-- Found gts: /usr/lib/
-- Use system gts version
-- Found minieigen: /usr/lib/
-- Found Tkinter: /usr/lib/
-- VTK version >5 and <8 is found
-- =======
-- Yade configured with following features: Odeint VTK OpenMP GTS GUI-Qt5 CGAL PFVFLOW LINSOLV TWOPHASEFLOW SPH DEFORM LIQMIGRATION GL2PS LBMFLOW MASK_ARBITRARY PROFILING PotentialParticles PotentialBlocks
-- Disabled features: CHOLMOD_GPU THERMAL
-- Optimized build
-- =======
-- Configuring done
-- Generating done
-- Build files have been written to: /home/yufan/
Is there any issue reflected from the above output that would be related to the problem?
Thanks for your concerning!
Revision history for this message
|
#10 |
@Bruno Chareyre @Jan Stránský
I want to provide additional information that the Ubuntu is running through a Vmware (virtual machine).
Is it correlated with the problem?
Revision history for this message
|
#11 |
> Actually, I tried to install 2019 at first, but I encountered the problem that I described above. Then I turned to a different version (2018.02b) and the same problem occurred.
my note was about trying different version of **operating system**, not Yade. In your case, you have quite new Yade version running on quite old Ubuntu. There could be some mismatch with used libraries (new Yade expecting something which is not present yet on the system).
The problem is, that nobody will happy to trying this case, not saying about fixing the issue..
cheers
Jan
Revision history for this message
|
#12 |
@Jan Stránský
Thank you all very much!