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] Cannot compile qt-x11-free-3.3.0
Date: Tue, 13 Apr 2004 19:48:00 -0000 [thread overview]
Message-ID: <20040413184406.10869.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-13 18:44 -------
Subject: Re: Cannot compile qt-x11-free-3.3.0
"geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> So, the appropriate fix for *this* bug is to backport RTH's change to the 3.4 branch?
I think we have some sort of mutual misunderstanding as to what this
PR represents.
If we interpret this PR as being specific to i686-pc-linux-gnu, then,
yes, backporting RTH's changes would fix it.
However, this bug exists because one of the gcc 3.4 release criteria
was that gcc 3.4 be able to compile QT, as described here:
http://gcc.gnu.org/gcc-3.4/criteria.html
Personally, I would interpret that as meaning that QT should build on
each relevant primary evaluation platform, which includes
i386-unknown-freebsd among other non-GNU/Linux systems.
This PR was filed because of a test of the release criteria, not
because of a specific GNU/Linux issue. See the initial report in the
PR.
Backporting RTH's fix would be a good idea. And it would fix this PR
as narrowly construed. But it would not fix the idea behind this PR,
which is that QT compile with gcc 3.4 on all relevant systems. That's
why I haven't pushed to backport RTH's fix: because the PR, in the
general case, isn't fixed in mainline, either. I think that fixing it
properly in mainline is a prerequisite to fixing it in 3.4.
Ian
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400
next prev parent reply other threads:[~2004-04-13 18:44 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
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 [this message]
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=20040413184406.10869.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).