I have C5 64-bit running on my laptop and am trying to get k3b 1.0.3 compiled from source. It keeps complaining about qt not being installed or available. I performed a yum install of everything qt, but it still complains.
I've read some postings on various web pages about creating symlinks, but although tried, that still didn't fix any problems.
What am I missing?
Thhanks.
Scott
Scott Ehrlich wrote:
I have C5 64-bit running on my laptop and am trying to get k3b 1.0.3 compiled from source. It keeps complaining about qt not being installed or available. I performed a yum install of everything qt, but it still complains.
I've read some postings on various web pages about creating symlinks, but although tried, that still didn't fix any problems.
What am I missing?
Last time I compiled a KDE app from source (knights I believe) I had to specify the Qt development lib path manually with an option to 'configure'.
Run a configure --help and look for the Qt lib options.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
Ross S. W. Walker pisze:
Last time I compiled a KDE app from source (knights I believe) I had to specify the Qt development lib path manually with an option to 'configure'.
a) in Red Hat Qt sources are in /usr/lib/qt-3.3 directory, but generally in distributions there is /usr/lib/qt path; all you need is symlink and forget of configure path options:
ln -s /usr/lib/qt-3.3 /usr/lib/qt
b) or
./cnfigure --with-qt-dir=/usr/lib/qt-3.3/
On Wed, 17 Oct 2007, Lukasz wrote:
Ross S. W. Walker pisze:
Last time I compiled a KDE app from source (knights I believe) I had to specify the Qt development lib path manually with an option to 'configure'.
a) in Red Hat Qt sources are in /usr/lib/qt-3.3 directory, but generally in distributions there is /usr/lib/qt path; all you need is symlink and forget of configure path options:
ln -s /usr/lib/qt-3.3 /usr/lib/qt
b) or
./cnfigure --with-qt-dir=/usr/lib/qt-3.3/
I'll try those.
Next error I get is kdelibs is not installed (which it is), or the version of qt installed doesn't exactly match the one kdelibs was compiled with (everything was yum installed).
Again, the system is running 64-bit C5 as a complete yum install, no individually compiled apps, unless/until I get k3b worked out.
Thanks for any help with kdelibs.
Scott
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Scott Ehrlich wrote:
On Wed, 17 Oct 2007, Lukasz wrote:
Ross S. W. Walker pisze:
Last time I compiled a KDE app from source (knights I believe) I had to specify the Qt development lib path manually with an option to 'configure'.
a) in Red Hat Qt sources are in /usr/lib/qt-3.3 directory, but generally in distributions there is /usr/lib/qt path; all you need is symlink and forget of configure path options:
ln -s /usr/lib/qt-3.3 /usr/lib/qt
b) or
./cnfigure --with-qt-dir=/usr/lib/qt-3.3/
I'll try those.
Next error I get is kdelibs is not installed (which it is), or the version of qt installed doesn't exactly match the one kdelibs was compiled with (everything was yum installed).
Again, the system is running 64-bit C5 as a complete yum install, no individually compiled apps, unless/until I get k3b worked out.
Thanks for any help with kdelibs.
Keep in mind that you need all the relevant *-devel files installed to BUILD things ... not just kdelibs and qt, but kdelibs-devel, kdebase-devel, qt-devel, etc.
Why do you need to build the new k3b ... we have one in centos and there is kde-redhat repo?
On Wed, 17 Oct 2007, Johnny Hughes wrote:
Scott Ehrlich wrote:
On Wed, 17 Oct 2007, Lukasz wrote:
Ross S. W. Walker pisze:
Last time I compiled a KDE app from source (knights I believe) I had to specify the Qt development lib path manually with an option to 'configure'.
a) in Red Hat Qt sources are in /usr/lib/qt-3.3 directory, but generally in distributions there is /usr/lib/qt path; all you need is symlink and forget of configure path options:
ln -s /usr/lib/qt-3.3 /usr/lib/qt
b) or
./cnfigure --with-qt-dir=/usr/lib/qt-3.3/
I'll try those.
Next error I get is kdelibs is not installed (which it is), or the version of qt installed doesn't exactly match the one kdelibs was compiled with (everything was yum installed).
Again, the system is running 64-bit C5 as a complete yum install, no individually compiled apps, unless/until I get k3b worked out.
Thanks for any help with kdelibs.
Keep in mind that you need all the relevant *-devel files installed to BUILD things ... not just kdelibs and qt, but kdelibs-devel, kdebase-devel, qt-devel, etc.
Why do you need to build the new k3b ... we have one in centos and there is kde-redhat repo?
I have found, over time, functionality of the k3b versions < 1.x.x (i.e. what is included in the distro) have caused failed or problematic burns somewhere during the process. I have had very successful runs with 1.x.x versions that have been manually compiled, though on 32-bit systems, and thus haven't experienced the compilation problems I'm dealing with now.
If I can get a 1.x.x version from a reliable repo, I'll be glad to try it.
Scott
On Wed, 17 Oct 2007 07:19:11 -0400 (EDT) Scott Ehrlich scott@MIT.EDU wrote:
I have found, over time, functionality of the k3b versions < 1.x.x (i.e. what is included in the distro) have caused failed or problematic burns somewhere during the process.
Then it's not k3b that's causing your problem and you are barking up the wrong tree altogether.
k3b is merely a front-end for several programs, chiefly mkisofs and cdrecord. It is mkisofs and cdrecord that do all of the actual work when it comes to burning a CD and if you are having failures then that is where you should be looking.
Actually, the problem will more likely be found at your cd burner and the quality of the cdr's that you are using than any of the software.
-
Frank Cox -
Johnny Hughes -
Lukasz -
Ross S. W. Walker -
Scott Ehrlich