Bug 97550

Summary: telepathy-qt 0.9.7 fails to build due to an linking error
Product: Telepathy Reporter: David GEIGER <geiger.david68210>
Component: tp-qtAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: 0.9   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: proposal patch to fix build

Description David GEIGER 2016-08-31 15:12:57 UTC 
Hi,

On Mageia we tried to build latest telepathy-qt 0.9.7 but we get an linking error (undefined reference to `Tp::Object::staticMetaObject'):

http://pastebin.com/1SgMRAGs


This issue seems to happens since latest change of telepathy-qt-service library from STATIC to SHARED.


So we have found how to fix this issue to build with "-Wl,--no-undefined" LD flags enabled:

http://svnweb.mageia.org/packages/cauldron/telepathy-qt/current/SOURCES/0100-Fix-tp-service-build-with-Wl-no-undefined.patch?view=markup&pathrev=1049562

Comlpiled with GCC 5.4.0, Qt5 5.6.1.


Best regards,
David
Comment 1 David GEIGER 2016-08-31 15:14:25 UTC 
Created attachment 126134 [details] [review]
proposal patch to fix build
Comment 2 Alexandr Akulich 2016-08-31 15:56:37 UTC 
Yeah, you're right. I also found the bug two days ago. 

I had a lot of undefined references, e.g. to Tp::AvatarSpec(), which is a part of the main TpQt library, but used by Service e.g. at BaseProtocolAvatarsInterface.

I'm going to revert the commit 88e1c41725559cd625af02e35863e596fb60d1e0 in a hour.
Comment 3 Alexandr Akulich 2016-08-31 18:39:55 UTC 
Fixed by commit 00b5b425275f154b013365c944a67851c77d5ab2.

David, thank you for the report! I think I need to build the project with your options to find such errors. Currently I build with default flags without problems.

https://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=00b5b425275f154b013365c944a67851c77d5ab2

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.