public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at wasabisystems dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/14400] [3.4/3.5 regression] Cannot compile qt-x11-free-3.3.0
Date: Wed, 07 Apr 2004 18:53:00 -0000 [thread overview]
Message-ID: <20040407185316.30137.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de>
------- Additional Comments From ian at wasabisystems dot com 2004-04-07 18:53 -------
Subject: Re: [3.4/3.5 regression] Cannot compile qt-x11-free-3.3.0
"mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> Can QT be compiled if PCH is explicitly not used?
>
> In other words, could the QT Makefiles work around this problem by not using a
> PCH file?
I have confirmed that, if I comment out the line in the QT configure
script where QT tests for PCH support, the build gets past the
previous point of failure, using the 3.4 branch compiler on
i686-pc-linux-gnu. QT takes forever to build on my system; I will
report back in this PR if there is any failure later in the build.
Pending that, the answer to your question is "yes."
For the record, the change I made to the configure script was to
comment out this line:
$unixtests/precomp.test $XQMAKESPEC $OPT_VERBOSE || QMAKE_CONFIG="$QMAKE_CONFIG precompile_header"
precomp.test is a fairly simple test which checks to see whether the
compiler accepts "-x c-header" and "-x c++-header". I don't see any
obvious way to use a command line argument to affect the test result.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400
next prev parent reply other threads:[~2004-04-07 18:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 8:35 [Bug pch/14400] New: " schmid at snake dot iap dot physik dot tu-darmstadt dot de
2004-03-03 12:40 ` [Bug pch/14400] " giovannibajo at libero dot it
2004-03-03 16:44 ` pinskia at gcc dot gnu dot org
2004-03-04 6:07 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de
2004-03-04 7:03 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de
2004-03-17 5:50 ` mmitchel at gcc dot gnu dot org
2004-03-17 5:56 ` pinskia at gcc dot gnu dot org
2004-03-25 6:57 ` pinskia at gcc dot gnu dot org
2004-03-26 8:01 ` schmid at snake dot iap dot physik dot tu-darmstadt dot de
2004-03-27 7:03 ` ian at wasabisystems dot com
2004-03-30 1:42 ` geoffk at gcc dot gnu dot org
2004-03-30 7:07 ` ian at wasabisystems dot com
2004-04-01 1:17 ` geoffk at apple dot com
2004-04-02 15:18 ` ian at wasabisystems dot com
2004-04-02 19:16 ` geoffk at apple dot com
2004-04-04 3:39 ` ian at wasabisystems dot com
2004-04-05 20:40 ` [Bug pch/14400] [3.4 regression] " ian at wasabisystems dot com
2004-04-05 20:54 ` mrs at apple dot com
2004-04-05 22:50 ` geoffk at apple dot com
2004-04-06 0:39 ` ian at wasabisystems dot com
2004-04-06 13:34 ` [Bug pch/14400] [3.4/3.5 " ian at wasabisystems dot com
2004-04-07 18:01 ` mmitchel at gcc dot gnu dot org
2004-04-07 18:34 ` mueller at kde dot org
2004-04-07 18:53 ` ian at wasabisystems dot com [this message]
2004-04-07 19:21 ` mark at codesourcery dot com
2004-04-07 19:22 ` [Bug pch/14400] " pinskia at gcc dot gnu dot org
2004-04-07 19:35 ` ian at wasabisystems dot com
2004-04-07 20:44 ` ian at wasabisystems dot com
2004-04-12 21:11 ` mmitchel at gcc dot gnu dot org
2004-04-12 22:07 ` geoffk at gcc dot gnu dot org
2004-04-12 22:45 ` ian at wasabisystems dot com
2004-04-12 23:13 ` geoffk at apple dot com
2004-04-13 15:07 ` ian at wasabisystems dot com
2004-04-13 18:38 ` geoffk at gcc dot gnu dot org
2004-04-13 19:48 ` ian at wasabisystems dot com
2004-04-13 19:53 ` geoffk at gcc dot gnu dot org
2004-05-29 22:54 ` [Bug pch/14400] [pch] " mmitchel at gcc dot gnu dot org
2004-06-18 23:57 ` mmitchel at gcc dot gnu dot org
2004-08-23 20:55 ` mmitchel at gcc dot gnu dot org
2004-11-01 0:47 ` mmitchel at gcc dot gnu dot org
2005-04-14 0:28 ` pinskia at gcc dot gnu dot org
2005-05-19 17:50 ` mmitchel at gcc dot gnu dot org
2005-08-02 19:04 ` cvs-commit at gcc dot gnu dot org
2005-08-02 19:05 ` ian at airs dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040407185316.30137.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).