Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#38384 - [qtractor] Doesn't build when qt5 is installed

Attached to Project: Community Packages
Opened by rob.til.freedman (rtfreedman) - Saturday, 04 January 2014, 22:08 GMT
Last edited by Ray Rashif (schivmeister) - Tuesday, 01 April 2014, 06:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ray Rashif (schivmeister)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

configure fails to find proper qt4 libs when qt5-base is installed.
configure defaults to look at /usr/lib/qt - which for some unknown reason defaults to qt5 in Arch.
We have more than 200 packages requiring qt4 - but less than 10 based on qt5 (not counting qt5 supporting libs)
Why isn't /usr/lib/qt a symlink to /usr/lib/qt4 and qt5 placed in /usr/lib/qt5 ?

This task depends upon

Closed by  Ray Rashif (schivmeister)
Tuesday, 01 April 2014, 06:10 GMT
Reason for closing:  Fixed
Comment by Ray Rashif (schivmeister) - Thursday, 09 January 2014, 08:52 GMT
Thanks for reporting this. I forgot the developer (Rui) propagates changes across all his stuff. Qt actually provides tools to select the version -- we select qt5 by default because it is current. You can select the version with QT_SELECT=$majorver or with a config file. [1]

I struggled with qsampler in AUR to come up with something sane but ended up manipulating configure. I will have to check whether it is the buildsystem that needs fixing or some obvious trick we're missing. In the meantime, please change your symlinks.

[1] https://wiki.archlinux.org/index.php/Qt#Installation
Comment by rob.til.freedman (rtfreedman) - Thursday, 09 January 2014, 21:58 GMT
export QT_SELECT=4 doesn't work with qtractor - it's the way configure is looking for the libs that doesn't work with Arch's setup of qt libs.

My complain here is, your PKGBUILD doesn't work unless qt5 is removed or used in a chroot.

@Qt actually provides tools to select the version...
No reason than to place the libs in qt/ instead of qt5/

@I struggled with qsampler in AUR to come up with something sane...
As I did with qtractor - I've used:
sed 's/^ac_qtdirs="qt"/ac_qtdirs="qt4"/' -i configure
Comment by Ray Rashif (schivmeister) - Friday, 10 January 2014, 10:14 GMT
@export QT_SELECT=4 doesn't work with qtractor
Like I said, Rui propagates the same changes, so they're all affected. I didn't notice this earlier because builds are all done in chroots.

@your PKGBUILD doesn't work unless qt5 is removed or used in a chroot
Right, I shouldn't have mentioned symlinks; they have no effect at all. I actually meant to suggest following the qsampler hack or building in a chroot.

@No reason than to place the libs in qt/ instead of qt5/
Bring this up with the qt maintainer :) This is done with the qtchooser package, so file a report against that.

@As I did with qtractor
Yes, keep doing that for now until I get in touch with upstream.
Comment by Ray Rashif (schivmeister) - Monday, 17 February 2014, 06:47 GMT
So we'll go with our hack; there is no known better solution. [1]

[1] http://www.rncbc.org/drupal/node/753

Loading...