Bug 179550 - Threading broken with current Qt3
Summary: Threading broken with current Qt3
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: qt
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-01 11:25 UTC by Paul F. Johnson
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-20 11:07:40 UTC


Attachments (Terms of Use)
Example program which fails to compile (6.16 KB, application/x-zip-compressed)
2006-02-01 11:25 UTC, Paul F. Johnson
no flags Details

Description Paul F. Johnson 2006-02-01 11:25:44 UTC
Description of problem:
Using a simple test example provided in C++ GUI Programming using Qt (attached
to this bug), it appears that threading is either not enabled or broken with the
current rawhide release version of Qt.

Version-Release number of selected component (if applicable):
3.3.5-12

How reproducible:
Always

Steps to Reproduce:
1. Attempt to compile the attached code
  
Actual results:
Various errors concerning the Qt Mutex and Threading classes are generated

Expected results:
It should compile.

Additional info:

I have tested this against a sandbox install of Qt3 from the Trolltech website
and the code compiles and runs without a problem. Code compiled on an x86_64
box, untested on an x86 machine.

Comment 1 Paul F. Johnson 2006-02-01 11:25:44 UTC
Created attachment 123955 [details]
Example program which fails to compile

Comment 2 Rahul Sundaram 2006-02-20 11:07:40 UTC

These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks


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