linphone-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Python API Compilation problems


From: Ghislain MARY
Subject: Re: [Linphone-developers] Python API Compilation problems
Date: Thu, 4 Feb 2016 12:13:54 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1

Hi Loïc,

I don't think this issue comes from the nm messages. In fact, these messages are just warnings that should not even be printed. I would need to make a pass on this some day.
To understand the issue, could you run the command `ldd linphone.so` in the lib/python2.7/site-packages/linphone directory of the prefix of the python installation where you installed the wheel package?
That will list all the shared libraries on which the linphone python module depends and where they are looked for.

Cheers,
Ghislain

On 02/03/2016 11:08 AM, Loïc Maudou wrote:
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

2016-02-02 16:45 GMT+01:00 Ghislain MARY <address@hidden>:
Hi Loïc,

You need to build the speex library from the linphone branch of the git://git.linphone.org/speex.git repository.

Cheers,
Ghislain


On 02/02/2016 16:10, Loïc Maudou wrote:
Hi,
I'm trying to compile python API for a raspberry pi 2 working with archlinux with video display support (I heard the already compiled version cannot display video).
I'm using cross compilation from an Archlinux computer using a toolchain generated by crosstool-ng.
I did manage to finish the process, but I get this strange warning during pylinphone configuration:

nm: « linphone »: pas de tel fichier (means "No such file" in french)
nm: « mediastreamer_base »: pas de tel fichier
nm: « mediastreamer_voip »: pas de tel fichier
nm: « ortp »: pas de tel fichier
nm: « bzrtp »: pas de tel fichier
nm: « bellesip »: pas de tel fichier
nm: « linphone »: pas de tel fichier
nm: « mediastreamer_base »: pas de tel fichier
nm: « mediastreamer_voip »: pas de tel fichier
nm: « ortp »: pas de tel fichier
nm: « bzrtp »: pas de tel fichier
nm: « bellesip »: pas de tel fichier

The installation of the wheel package works, but when I try to import linphone, I get this error message :

>>> from linphone import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/linphone/__init__.py", line 1, in <module>
    from linphone import *
ImportError: /usr/lib/python2.7/site-packages/linphone/linphone.so: undefined symbol: speex_echo_state_blob_get_data
b_get_data

It looks like the librairy where not used by pylinphone... I've been looking for the cause those 3 days but did not manage to find it...

Thanks in advance for your help !

Loïc


_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers




_______________________________________________
Linphone-developers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-developers


reply via email to

[Prev in Thread] Current Thread [Next in Thread]