Bug 179494 - qmake broken
Summary: qmake broken
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: qt
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-31 20:31 UTC by Paul F. Johnson
Modified: 2015-07-17 21:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-20 12:03:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Example .pro file (385 bytes, text/plain)
2006-01-31 20:31 UTC, Paul F. Johnson
no flags Details
Zip file containing the example I'm trying to compile using qmake (6.16 KB, application/x-zip)
2006-01-31 20:33 UTC, Paul F. Johnson
no flags Details

Description Paul F. Johnson 2006-01-31 20:31:42 UTC
Description of problem:
When running qmake all I get is QFile::open : no file name specified. I am
trying to compile against the examples in "C++ GUI Programming with Qt3"

Version-Release number of selected component (if applicable):
qmake 1.0.7a
qt 3.3.5-12

How reproducible:
Always

Steps to Reproduce:
1. qmake -o Makefile <filename>.pro
  
Actual results:
QFile::open : no file name specified

Expected results:
A make file should be generated

Additional info:
I've not tested this on an x86 box

Comment 1 Paul F. Johnson 2006-01-31 20:31:43 UTC
Created attachment 123936 [details]
Example .pro file

Comment 2 Paul F. Johnson 2006-01-31 20:33:07 UTC
Created attachment 123937 [details]
Zip file containing the example I'm trying to compile using qmake

Comment 3 Than Ngo 2006-02-20 12:03:43 UTC
i have tried to compile your zip file with the current rawhide from today, it
works fine for me. It's tested on x86_64 plattform. You should please update 
to current rawhide. Thanks

Comment 4 Richard Jasmin 2015-07-17 21:34:30 UTC
Current rawhide can sometimes break as its rawhide, not stable.Next time provide a snapshot version id.


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