Bug 653674 - Fails to create debug build of Qt projects on mingw
Summary: Fails to create debug build of Qt projects on mingw
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qt
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-15 22:19 UTC by Ivan Romanov
Modified: 2013-10-04 00:46 UTC (History)
12 users (show)

Fixed In Version: qt-4.7.1-3.fc14
Clone Of:
Environment:
Last Closed: 2010-11-28 20:43:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch to fix QTBUG-14467 (1.56 KB, patch)
2010-11-15 22:19 UTC, Ivan Romanov
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Qt Bug Tracker QTBUG-14467 0 None None None Never

Description Ivan Romanov 2010-11-15 22:19:42 UTC
Created attachment 460681 [details]
Patch to fix QTBUG-14467

Description of problem:
See upstream bug http://bugreports.qt.nokia.com/browse/QTBUG-14467.
They silent for one month. While they thinking I make patch to fix it. See in attachments.

Comment 1 Kevin Kofler 2010-11-23 19:43:03 UTC
So, my understanding is that the Fedora MinGW maintainers would like us to apply this patch to our qt package, is that correct?

If it is so, since it shouldn't affect anybody else, I'm OK with applying that patch to our Qt packaging. I'd prefer this to get sorted out upstream, but I'm OK with the patch if the MinGW folks are convinced it's right.

(I personally have some reservations about a variable named $${QT_LIBINFIX} being made a postfix though. MinGW folks: are you sure this makes sense?)

Comment 2 Erik van Pienbroek 2010-11-23 20:01:38 UTC
> So, my understanding is that the Fedora MinGW maintainers would like us to
> apply this patch to our qt package, is that correct?

That's correct

> If it is so, since it shouldn't affect anybody else, I'm OK with applying that
> patch to our Qt packaging. I'd prefer this to get sorted out upstream, but I'm
> OK with the patch if the MinGW folks are convinced it's right.
> 
> (I personally have some reservations about a variable named $${QT_LIBINFIX}
> being made a postfix though. MinGW folks: are you sure this makes sense?)

We've asked upstream in the mentioned bugreport what the correct behaviour should be (should the suffix be 'd4' of '4d'? where does the '4' come from?). Unfortunately we haven't seen any response to that question so our best guess is to work around it in the qmake mkspecs files for now until upstream provides more information.

The win32 binaries provided by upstream all use the suffix 'd4' as well so our packaging looks okay from that point of view

Comment 3 Kevin Kofler 2010-11-23 20:13:24 UTC
I guess that's enough justification for me, let's apply the patch. What do the other Qt comaintainers think?

Comment 4 Rex Dieter 2010-11-23 20:28:01 UTC
fine with me, let's do it.

Comment 5 Jaroslav Reznik 2010-11-24 15:21:58 UTC
+1

Comment 6 Fedora Update System 2010-11-24 17:03:06 UTC
qt-4.7.1-3.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/qt-4.7.1-3.fc14

Comment 7 Fedora Update System 2010-11-26 01:10:28 UTC
qt-4.7.1-3.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update qt'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/qt-4.7.1-3.fc14

Comment 8 Ivan Romanov 2010-11-26 10:58:15 UTC
I installed qt-4.7.1-3.fc14.x86_64. I do test and it's now work. Thank!

Comment 9 Fedora Update System 2010-11-28 20:42:55 UTC
qt-4.7.1-3.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Red Hat Bugzilla 2013-10-04 00:19:33 UTC
Removing external tracker bug with the id '14467' as it is not valid for this tracker


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