Hello,
I've started writing ebuilds for trinity, but failed at tqtinterface (damn!). I've successfully built it before, but now it seems that the build script do not compile libtqt.so.*, only symlinks to it. This reminds me some old bugs with configure (sigh). I think this might be problem with our eclasses, but the same happens with recommended steps to build. Maybe buggy libtool? Using 2.2.10.
Attaching log.
Regards Ladislav Laska S pozdravem Ladislav Laska --- xmpp/jabber: ladislav.laska@jabber.cz
Hello,
I've started writing ebuilds for trinity, but failed at tqtinterface (damn!). I've successfully built it before, but now it seems that the build script do not compile libtqt.so.*, only symlinks to it. This reminds me some old bugs with configure (sigh). I think this might be problem with our eclasses, but the same happens with recommended steps to build. Maybe buggy libtool? Using 2.2.10.
Attaching log.
Strange! It looks like it compiles, but it only leaves dangling symlinks when the compilation completes?
Can you send over the output of: find . executed in the top source directory after build?
Thanks!
Tim
Seems that way. I have no idea why.
I'm attaching find log. Also, if you want to see what was generated, I've uploaded compiled version (just after build)
http://stuff.krakonos.org/files/tqt-build.tar.gz
(will be deleted after a week)
Regards Ladislav Laska S pozdravem Ladislav Laska --- xmpp/jabber: ladislav.laska@jabber.cz
On Mon, Oct 4, 2010 at 7:22 PM, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Hello,
I've started writing ebuilds for trinity, but failed at tqtinterface (damn!). I've successfully built it before, but now it seems that the build script do not compile libtqt.so.*, only symlinks to it. This reminds me some old bugs with configure (sigh). I think this might be problem with our eclasses, but the same happens with recommended steps to build. Maybe buggy libtool? Using 2.2.10.
Attaching log.
Strange! It looks like it compiles, but it only leaves dangling symlinks when the compilation completes?
Can you send over the output of: find . executed in the top source directory after build?
Thanks!
Tim
On Monday 04 October 2010 13:35:56 Ladislav Laska wrote:
Hello,
I've started writing ebuilds for trinity, but failed at tqtinterface (damn!). I've successfully built it before, but now it seems that the build script do not compile libtqt.so.*, only symlinks to it. This reminds me some old bugs with configure (sigh). I think this might be problem with our eclasses, but the same happens with recommended steps to build. Maybe buggy libtool? Using 2.2.10.
Attaching log.
If i'm not wrong, this problem appear for autoconf > 2.63 Also, when you will using autoconf 2.63, autotools will not find qt, because qt presence is not checking for /usr/qt/3
Right now you can create ebuild using my cmake work: http://github.com/serghei/kde-trinity/blob/master/kde-base/tqtinterface/tqti...
I thought it was fixed. Well, I may have overlooked it.
Well, I'd like to have ebuilds from official packages, so it will be simple enough to migrate to new version. I'll give it a little bit more time and digging.
Regards Ladislav Laska S pozdravem Ladislav Laska --- xmpp/jabber: ladislav.laska@jabber.cz
On Mon, Oct 4, 2010 at 10:37 PM, Serghei Amelian serghei@thel.ro wrote:
On Monday 04 October 2010 13:35:56 Ladislav Laska wrote:
Hello,
I've started writing ebuilds for trinity, but failed at tqtinterface (damn!). I've successfully built it before, but now it seems that the build script do not compile libtqt.so.*, only symlinks to it. This reminds me some old bugs with configure (sigh). I think this might be problem with our eclasses, but the same happens with recommended steps to build. Maybe buggy libtool? Using 2.2.10.
Attaching log.
If i'm not wrong, this problem appear for autoconf > 2.63 Also, when you will using autoconf 2.63, autotools will not find qt, because qt presence is not checking for /usr/qt/3
Right now you can create ebuild using my cmake work: http://github.com/serghei/kde-trinity/blob/master/kde-base/tqtinterface/tqti...
-- Serghei