Bug 324661 - amarok: Build is broken in the Qt3/Qt4 combined environment
Summary: amarok: Build is broken in the Qt3/Qt4 combined environment
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-09 10:41 UTC by Andy Shevchenko
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-11 13:03:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andy Shevchenko 2007-10-09 10:41:12 UTC
Description of problem:
When I try to build amaroK in the Qt3/Qt4 combined environment the amaroK is 
catching incorrect headers.

Version-Release number of selected component (if applicable):
Last official package

Additional info:
I think a workaround may be added such as Confilts: qt4-devel

Comment 1 Rex Dieter 2007-10-09 14:03:10 UTC
Patient: My arm hurts when I move it like this.
Dr: Then don't do that! 
:)

Either use a clean build environment (like mock), or be aware that qt3/qt4 devel
environments being installed side-by-side has some short-comings.

I suspect the problem goes away if one does (before calling ./configure; make):
export PATH=$QTDIR/bin:$PATH

Comment 2 Andy Shevchenko 2007-10-09 15:22:56 UTC
(In reply to comment #1)
Some environments (I'd like to say "exclusive environments") requires the Qt3 
as well as Qt4 installed at the same time.


Comment 3 Rex Dieter 2007-10-09 15:28:02 UTC
Qt3/Qt4 runtime or Qt3/Qt4 Development environments?  :)  The former should
always "just work", the latter is where things get hairy.

Comment 4 Andy Shevchenko 2007-11-11 13:03:13 UTC
I decide to close this report  because of many packages are not building in 
such environment - not only amarok. 


Note You need to log in before you can comment on or make changes to this bug.