I have to say things are getting better and i have been able to compile
most packages i could not before ... except k3b. I successfully compiled
around 2 weeks ago but today i get the error below error:
I have all dependencies installed:
libdvdcss, ffmpeg, lame, faac, faad2, speex, xvidcore, schroedinger,
openjpeg, and x264
# Install transcode.
# Transcode dependencies: ffmpeg, libmpeg2, lame, libdv, libdvdread, and
a52dec.
./misc/.libs/libmisc.a(k3bcdcopydialog.o): In function
`K3bCdCopyDialog::slotStartClicked()':
k3bcdcopydialog.cpp:(.text+0x30d3): undefined reference to
`K3bCdCopyJob::K3bCdCopyJob(K3bJobHandler*, QObject*)'
k3bcdcopydialog.cpp:(.text+0x38da): undefined reference to
`K3bCloneJob::K3bCloneJob(K3bJobHandler*, QObject*, char const*)'
./misc/.libs/libmisc.a(k3bdvdcopydialog.o): In function
`K3bDvdCopyDialog::slotStartClicked()':
k3bdvdcopydialog.cpp:(.text+0x22d4): undefined reference to
`K3bDvdCopyJob::K3bDvdCopyJob(K3bJobHandler*, QObject*, char const*)'
k3bdvdcopydialog.cpp:(.text+0x2415): undefined reference to
`K3bDvdCopyJob::setVerifyData(bool)'
./misc/.libs/libmisc.a(k3bcdimagewritingdialog.o): In function
`K3bCdImageWritingDialog::slotUpdateImage(QString const&)':
k3bcdimagewritingdialog.cpp:(.text+0x5244): undefined reference to
`K3bCloneTocReader::K3bCloneTocReader(QString const&)'
k3bcdimagewritingdialog.cpp:(.text+0x5329): undefined reference to
`K3bCloneTocReader::~K3bCloneTocReader()'
./misc/.libs/libmisc.a(k3bcdimagewritingdialog.o): In function
`K3bCdImageWritingDialog::slotStartClicked()':
k3bcdimagewritingdialog.cpp:(.text+0x68a8): undefined reference to
`K3bCloneJob::K3bCloneJob(K3bJobHandler*, QObject*, char const*)'
k3bcdimagewritingdialog.cpp:(.text+0x6a20): undefined reference to
`K3bAudioCueFileWritingJob::K3bAudioCueFileWritingJob(K3bJobHandler*,
QObject*, char const*)'
k3bcdimagewritingdialog.cpp:(.text+0x6a3a): undefined reference to
`K3bAudioCueFileWritingJob::setBurnDevice(K3bDevice::Device*)'
k3bcdimagewritingdialog.cpp:(.text+0x6a54): undefined reference to
`K3bAudioCueFileWritingJob::setSpeed(int)'
k3bcdimagewritingdialog.cpp:(.text+0x6a73): undefined reference to
`K3bAudioCueFileWritingJob::setSimulate(bool)'
k3bcdimagewritingdialog.cpp:(.text+0x6a8d): undefined reference to
`K3bAudioCueFileWritingJob::setWritingMode(int)'
k3bcdimagewritingdialog.cpp:(.text+0x6aa2): undefined reference to
`K3bAudioCueFileWritingJob::setCueFile(QString const&)'
k3bcdimagewritingdialog.cpp:(.text+0x6ac6): undefined reference to
`K3bAudioCueFileWritingJob::setCopies(int)'
k3bcdimagewritingdialog.cpp:(.text+0x6ae5): undefined reference to
`K3bAudioCueFileWritingJob::setOnTheFly(bool)'
k3bcdimagewritingdialog.cpp:(.text+0x6b15): undefined reference to
`K3bAudioCueFileWritingJob::setTempDir(QString const&)'
k3bcdimagewritingdialog.cpp:(.text+0x6b60): undefined reference to
`K3bBinImageWritingJob::K3bBinImageWritingJob(K3bJobHandler*, QObject*)'
k3bcdimagewritingdialog.cpp:(.text+0x6b97): undefined reference to
`K3bBinImageWritingJob::setTocFile(QString const&)'
k3bcdimagewritingdialog.cpp:(.text+0x6f4a): undefined reference to
`K3bIso9660ImageWritingJob::K3bIso9660ImageWritingJob(K3bJobHandler*)'
./misc/.libs/libmisc.a(k3bisoimagewritingdialog.o): In function
`K3bIsoImageWritingDialog::slotStartClicked()':
k3bisoimagewritingdialog.cpp:(.text+0x3a0e): undefined reference to
`K3bIso9660ImageWritingJob::K3bIso9660ImageWritingJob(K3bJobHandler*)'
collect2: ld returned 1 exit status
make[3]: *** [k3b] Error 1
make[3]: Leaving directory `/tmp/k3b/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/k3b/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/k3b'
make: *** [all] Error 2
Jay
Tim,
Please correct this package description.
=======================================
avahi-tqt (Avahi Trinity Qt Interface)
avahi-tqt is the Trinity Qt Interface layer for Avahi. This package ensures Avahi is usable against the (T)Qt3 libaries without rebuilding Avahi.
=======================================
Thanks!
Darrell
I have tried the autogen, autoconf and compile scripts, but both result in
a make error:
*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]: *** [qt-watch.moc3] Error 1*
It seems that qt-watch.moc3 does not exist at the end of this.
The only reference i could find to it is below but it offers no resolution.
http://trinity-users.pearsoncomputing.net/?0::2475
While compiling from latest git (20th Feb 2012) i got as far as tdebase. At
around the 90% mark it failed.
*git/tde/main/tdebase/tdm/backend/consolekit.c:31:23: fatal error:
dbus/dbus.h: No such file or directory
compilation terminated.*
consolekit.c contains the following include:
#include <dbus/dbus.h>
when the actual headers path is /usr/include/dbus-1.0/dbus/dbus.h
Rebuilding now with a symlink to see how far i get.
Jay
I would be grateful if somebody --- other than Tim --- would browse the web site and wiki, browse the various Trinity apps, and provide me a list of features that have been added or significantly modified since 3.5.10.
We will use that list to ensure those new or modified features are addressed in the various handbook help files.
No technical writing or editing required. No reviews of any help files required. Just a list of new or modified features. :)
Perhaps somebody could forward this request to the users list.
Thanks!
Darrell
Do we have such a team? Who are the Trinity art wizards?
As I revise the help files I'm finding many images deep in the sources that need updating to Trinity logos and identities to replace the KDE3 generation of art work.
I'm filing bug reports and submitting a handful of images I can change with my feeble graphics skills. Yet graphics is not my strong point and others with those skills could update these images much faster than me and provide professional results.
I see an opportunity here for people to contribute to the project by updating these many files for R14.
Is anybody interested?
Darrell
How will these packages be handled? Just another package in applications? A special web page at the Trinity web site?
I ask because there a few places in the handbook help files specifically referencing the kde-look.org web site. I want to know how to revise those snippets.
Darrell
