Hello,
First post to the ML.
I get this error trying to build arts 3.5.12 for unity linux/mandriva. From
what I have seen it looks like I maybe missing tqtinterface tqt-moc calling
moc, but I'm not sure how that is done.
libtool: link: g++ -shared -nostdlib
/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3/../../../crti.o
/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3/crtbeginS.o .libs/giomanager.o
-march=i586 -mtune=generic -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-O1
-Wl,--build-id -pthread -Wl,-rpath
-Wl,/home/unity/src/rpm/BUILD/arts-3.5.12/mcop/.libs -Wl,-rpath
-Wl,/opt/trinity/lib -L/opt/trinity/lib ../mcop/.libs/libmcop.so /usr/lib/
libgmodule-2.0.so /usr/lib/libgthread-2.0.so -lrt
/usr/lib/libglib-2.0.so-L/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3
-L/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3/../../.. -lstdc++ -lm -lc -lgcc_s
/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3/crtendS.o
/usr/lib/gcc/i586-manbo-linux-gnu/4.4.3/../../../crtn.o -Wl,-soname
-Wl,libgmcop.so.1 -o .libs/libgmcop.so.1.0.0
libtool: link: (cd ".libs" && rm -f "libgmcop.so.1" && ln -s
"libgmcop.so.1.0.0" "libgmcop.so.1")
libtool: link: (cd ".libs" && rm -f "libgmcop.so" && ln -s
"libgmcop.so.1.0.0" "libgmcop.so")
libtool: link: ( cd ".libs" && rm -f "libgmcop.la" && ln -s "../libgmcop.la"
"libgmcop.la" )
make[2]: Leaving directory `/home/unity/src/rpm/BUILD/arts-3.5.12/gmcop'
Making all in qtmcop
make[2]: Entering directory `/home/unity/src/rpm/BUILD/arts-3.5.12/qtmcop'
/usr/lib/qt3/bin/moc ./qiomanager_p.h qiomanager_p.moc
Qt meta object compiler
moc: Too many input files specified
Usage: moc [options] <header-file>
-o file Write output to file rather than stdout
-f[file] Force #include, optional file name
-p path Path prefix for included file
-i Do not generate an #include statement
-k Do not stop on errors
-nw Do not display warnings
-v Display version of moc
make[2]: *** [qiomanager_p.moc] Error 1
make[2]: Leaving directory `/home/unity/src/rpm/BUILD/arts-3.5.12/qtmcop'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/unity/src/rpm/BUILD/arts-3.5.12'
make: *** [all] Error 2
error: Bad exit status from /home/unity/src/tmp/rpm-tmp.9958 (%build)
Regard,
Matthew Dawkins
Trinity svn has no source files for building qt3, dbus-qt3, etc. Why is building those files unnecessary in Debian/Kubuntu but necessary in Slackware? Or is rebuilding necessary in those systems too but the source files simply are not included in trinity?
Thanks.
Darrell
aLinux http://alinux.tv/ , a KDE3-centric distro indicates that they use KDE
3.5.12 as the main desktop. This unambiguously hints that they use Trnity.
Since aLinux is an RPM-based distro, this fact may make porting to other
RPM-based distributions easier as they provide SRPMs for each package.
Hi all,
I'm very new here and to Trinity so please be gentle, this is my first
attempt :-)
I'm attempting a build for Mandriva 2010.1 and by a long winded-process of
'hit and miss' I've managed to get .configure to run to completion except
for the following warning message regarding 'libtqtinterface-dev' needing
to be installed:
==== Caution wrapped ====
checking if TQt is available... no
configure: WARNING: You are attempting to compile Trinity without the
Trinity Qt Interface installed. Please install libtqtinterface-dev and
try again!
====
Ignoring this message and calling 'make' appears to complete
correctly, however 'make install' returns the following:
failure as follows:
=====Caution may wrap ====
[root@john tqtinterface]# make install
Making install in libltdl
make[1]: Entering directory `/spare/kde-3.5.12/dependencies/tqtinterface/libltdl'
make[2]: Entering directory `/spare/kde-3.5.12/dependencies/tqtinterface/libltdl'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/spare/kde-3.5.12/dependencies/tqtinterface/libltdl'
make[1]: Leaving directory `/spare/kde-3.5.12/dependencies/tqtinterface/libltdl'
Making install in qtinterface
make[1]: Entering directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
Making install in .
make[2]: Entering directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
make[3]: Entering directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
test -z "/usr/local/kde/lib" || /bin/mkdir -p "/usr/local/kde/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c -p libtqt.la '/usr/local/kde/lib'
libtool: install: /usr/bin/install -c -p .libs/libtqt.so.4.2.0 /usr/local/kde/lib/libtqt.so.4.2.0
/usr/bin/install: cannot stat `.libs/libtqt.so.4.2.0': No such file or directory
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface'
make: *** [install-recursive] Error 1
[root@john tqtinterface]#
I'm somewhat confused by the missing(?) `.libs/libtqt.so.4.2.0' message which is
correct when one looks in the referenced directory. Where does the ".2.0" come
from? What do I do to fix this?
==================
[root@john john]# locate libtqt
/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface/libtqt.la
/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface/.libs/libtqt.la
/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface/.libs/libtqt.lai
/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface/.libs/libtqt.so
/spare/kde-3.5.12/dependencies/tqtinterface/qtinterface/.libs/libtqt.so.4
[root@john john]#
Cheers
John NZ
Hi! I just found that KDE3 does not support IPv6.
knemo shows an interface as not connected if it has only IPv6 protocol.
Kconnections shows only IPv4 connections.
Although SVN provides a direct route to testing patches for the next 3.5.13 release, I want to propose making tarballs available too.
Many people are motivated to test newer versions but do not have the bandwidth, computer horsepower, or inclination to support SVN.
I propose providing directories just like those for downloading the 3.5.12 tarballs. The directories would be explicitly named 3.5.13-testing or something similar.
When 3.5.13 goes live and official, all we should need do is just change the name of the directory.
Darrell
Hello,
In this moment, cmake support for tqtinterface, arts and kdelibs are ready for
building tests.
Some info about cmake build system:
1) preffered mode for building are "out-of-source", which prevent sources to
be "polluted" with generated files and compiled objects (in kde4
out-of-source mode are mandatory).
For example, tqtinterfaces will be configured in this way:
mkdir /tmp/tqtinterface
cd /tmp/tqtinterface
svn co
svn://anonsvn.kde.org/home/kde/branches/trinity/dependencies/tqtinterface
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr ../tqtinterface
make -j 3
make install DESTDIR=/tmp/tqtinterface/install
2) There are some standard rules to activate/deactivate features:
For example, kdelibs have: WITH_LIBART, WITH_ARTS, WITH_TIFF, etc (for rest of
options check kdelibs/CMakeLists.txt)
For compile kdelibs with arts and tiff and without aspell, we will run:
cmake -DWITH_ARTS=ON -DWITH_TIFF=ON -DWITH_ASPELL=OFF <path_to_sources>
3) If we need to alter standard install directories we have variables like
BIN_INSTALL_DIR, SYSCONFDIR, XDG_MENUDIR.
Example:
cmake cmake -DCMAKE_INSTALL_PREFIX=/opt/kde3 -DSYSCONFDIR=/etc <sources>
4) Enabling RPATH:
cmake -DCMAKE_INSTALL_RPATH=/usr/kde/3.5/lib
###################################
(almost) complete example, kdelibs for ubuntu:
cmake -DCMAKE_INSTALL_PREFIX=/opt/kde3 \
-DINCLUDE_INSTALL_DIR=/opt/kde3/include/kde \
-DSYSCONFDIR=/etc \
-DWITH_LIBIDN=ON -DWITH_SSL=ON -DWITH_LIBART=ON \
-DWITH_ALSA=ON -DWITH_ARTS=ON -DWITH_CUPS=ON \
-DWITH_JASPER=ON -DWITH_OPENEXR=ON -DWITH_ASPELL=ON \
-DWITH_TIFF=ON -DWITH_LUA=OFF \
<path to kdelibs sources>
LUA support are disabled because is not done yet.
If you won't using RPATH, ensure that LD_LIBRARY_PATH is correcty set,
otherwise kdelibs will fail when will try to use mcopidl.
For testing, are preferable to use big number of concurrent compile processes
(-j 10, for example), to check if all dependencies are compiled in proper
order.
--
Serghei
Hi,
I've started to create/update spec files for Trinity KDE. You'll see some stuff
appearing in home:bravoall1552:trinity on build.o.o by the weekend.
I'll start out with SuSE and Fedora. I've got someone from the Unity Linux
project that can help Mandrivanize these :)
--
later, Robert Xu
Hello,
I wonder if is not good ideea to set RPATH into Trinity binaries, to
${prefix}/lib. In this case Trinity will still working even LD_LIBRARY_PATH
is not set at all.
Pros? Cons?
--
Serghei
