Closed
Bug 188830
Opened 22 years ago
Closed 22 years ago
[Qt] "configure" does not return an error when --enable-default-toolkit=qt is set but no libQt is available
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.3beta
People
(Reporter: roland.mainz, Assigned: netscape)
References
Details
Attachments
(1 file)
|
676 bytes,
patch
|
timeless
:
review+
|
Details | Diff | Splinter Review |
"configure" dopes not return an error when --enable-default-toolkit=qt is set
but no libQt is available.
Example:
-- snip --
checking for trouble comparing to zero near std::operator!=()... no
checking for LC_MESSAGES... yes
checking for main in -lqt... no
checking for main in no
checking Qt - version >= 2.2.0... yes
checking for freetype-config... no
checking for FreeType - version >= 6.1.0... no
-- snip --
Both tests for libQt ("-lqt" and "-lqt-mt") fail - but the configure script does
not return an error... ;-((
|
Assignee | |
Updated•22 years ago
|
Summary: [Qt] "configure" dopes not return an error when --enable-default-toolkit=qt is set but no libQt is available → [Qt] "configure" does not return an error when --enable-default-toolkit=qt is set but no libQt is available
|
|
Assignee | |
Comment 1•22 years ago
|
||
Attachment #111430 -
Flags: review+
|
|
Assignee | |
Comment 2•22 years ago
|
||
Patch has been checked in.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.3beta
|
||
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•