Message: previous - next
Month: March 2016

Re: [Bulk] Re: [trinity-devel] Help porting KDE3 app to trinity

From: Michele Calgaro <michele.calgaro@...>
Date: Mon, 21 Mar 2016 21:49:18 +0900
> Ummmmm....  sorry to be a PITA but it still doesn't compile for me out
> of the box (Debian Jessie with R14;0.3).
> I'm doing (and I'm not sure if this is the 'right' way):
> Make -f Makefile.cvs
> ./configure
> make
> and it fails with:
>> /usr/bin/tmoc ./TEPty.h -o TEPty.moc
>> /bin/sh ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.  -I.. -I. -I/opt/trinity/include -I/usr/share/tqt3/include -I. -include tqt.h   -DQT_THREAD_SUPPORT  -D_REENTRANT  -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -g -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt  -MT TEPty.lo -MD -MP -MF .deps/TEPty.Tpo -c -o TEPty.lo TEPty.cpp
>> libtool: Version mismatch error.  This is libtool 2.2.6b Debian-2.2.6b-2ubuntu1, but the
>> libtool: definition of this LT_INIT comes from libtool 2.4.2.
>> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b Debian-2.2.6b-2ubuntu1
>> libtool: and run autoconf again.
>> Makefile:886: recipe for target 'TEPty.lo' failed
> Jessie has libtool 2.4.2-1.11 installed and my PATH is:
> /opt/trinity/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/tract/ldb
> In an act of desperation :-) I copied /usr/src/k3b-trinity-14.0.3/obj-x86_64-linux-gnu/libtool
> (obtained from apt-get source k3b-trinity) to my klt directory and klt compiles and runs.
> So....  the bottom line is that I'm happy it compiles and runs but a
> little confused as to why the make/configure builds the wrong libtool.
> I'd like to know the 'right' way to fix this so it doesn't bite me going
> forward.
> Oh... I've just donated $500 to TDE as promised.
Hi Russell,
please try these other ways, using original code from Slavek.

1) go to klt folder. Type "debian/rules binary" and enter. If everything is ok it will compile and build a package at
the end
2) or try "dpkg-buildpackage -us -uc", once again from the same folder

This are more "stardard ways" to build a deb package locally, especially the second one.
Of course if you want to build in a clean chroot environment (THE debian way) you should use pbuilder/debuilder.