Re: Unresolved symbols which are present in linked libs

[Евгений Фарфель <jenfa@xxxxxxxxxxx>]

Hello!

Maybe, it will help someone with a similar problem someday :) This
issue was fixed by rebuilding telepathy-qt4 without
-fvisibility=hidden, which was placed in a gcc command line by cmake.
After I've removed it from CMakeLists, everything went fine.

2012/4/24 Ian Lance Taylor <iant@xxxxxxxxxx>:
> Евгений Фарфель <jenfa@xxxxxxxxxxx> writes:
>
>> I was not able to build it proper using your advice, though. If I
>> understand it correctly, you suggest to specify
>> -ltelepathy-qt4-farsight before -ltelepathy-qt4? I get the same error
>> messages that way. Should I fix my -l options ordering further? If so,
>> then how?
>
> Based on what you said before, putting -ltelepathy-qt4-farsight should
> fix the problem, or should at least give you different error messages.
> In general a -l option only resolves symbols left undefined by previous
> -l options, not by subsequent ones.
>
> Ian
>
>
>> 2012/4/24 Ian Lance Taylor <iant@xxxxxxxxxx>:
>>> Евгений Фарфель <jenfa@xxxxxxxxxxx> writes:
>>>
>>>> -ltelepathy-qt4
>>>> -ltelepathy-qt4-farsight -ltelepathy-glib
>>>
>>>> /home/user/workspace/playbook_prefix/lib/libtelepathy-qt4-farsight.so:
>>>> undefined reference to `Tp::DBusProxy::busName() const'
>>>
>>>> All those symbols should be present in libtelepathy-qt4
>>>
>>>
>>> The order of -l options matters.
>>>
>>> Ian