Hi Ghislain, as I already reported few weeks ago, I had the same problem as Loïc:
[ 95%] Performing configure step for 'TARGET_pylinphone'-- Using sysroot
path: /home/dima/workspace/intercom/linphone4raspberrypi//rootfs
CMake Error at CMakeLists.txt:36 (execute_process):
execute_process called with no value for WORKING_DIRECTORY.
nm: 'linphone': No such file
nm: 'mediastreamer_base': No such file
nm: 'mediastreamer_voip': No such file
nm: 'ortp': No such file
nm: 'bzrtp': No such file
nm: 'bellesip': No such file
nm: 'linphone': No such file
nm: 'mediastreamer_base': No such file
nm: 'mediastreamer_voip': No such file
nm: 'ortp': No such file
nm: 'bzrtp': No such file
nm: 'bellesip': No such file
CMake Error at CMakeLists.txt:209 (string):
string sub-command REPLACE requires at least four arguments.
I'm sorry about I can't answer earlier what I've done for building.
My system is Ubuntu 14.04.
I couldn't find the rootfs You mean. Hence I built rootfs from buildroot adding all needed libraries, discovering new dependencies arised through the process of linphone-cmake-builder and starting build again from clean.
Finally all packages were compiled, but wheel package building is stopped because incomprehensible 'nm' errors.
Ghislain, Thank You for Your involvement.
Best regards, Dmitriy Alekseev
From: Loïc Maudou <address@hidden>
To: address@hidden
Sent: Wednesday, February 3, 2016 1:08 PM
Subject: Re: [Linphone-developers] Python API Compilation problems
Hi Ghislain,
Thanks for your answer. I think that was already what I've done because speex is part of the linphone-cmake-builder package. I tried to recompile and copy the speex librairy to /usr/lib of the raspberry, but the error remains the same. Also, by making a wrong compilation, I had a preview of the message when he can find a librairy during the python linphone import :
/usr/lib/libswresample.so.1: version `LIBSWRESAMPLE_1' not found (required by /usr/lib/libavcodec.so.56)
I believe the origin of the problem comes from the "nm" warning during pylinphone configuration. As he cannot find the librairy, the symbols stay unknown for him. Do somebody have an idea of where is indicated the path to the librairy he had to find ? (I have to admit that my knowledge of cmake is quite weak...)
Thanks a lot for your help !
Loïc
Cet e-mail a été envoyé depuis un ordinateur protégé par Avast. www.avast.com |