public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schnetter at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/53919] Version-specific install instructions not available
Date: Thu, 12 Jul 2012 14:44:00 -0000 [thread overview]
Message-ID: <bug-53919-4-QEUqDRwujF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53919-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53919
Erik Schnetter <schnetter at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #8 from Erik Schnetter <schnetter at gmail dot com> 2012-07-12 14:43:59 UTC ---
I disagree with this assessment that this report is invalid. This is not a
complaint that I couldn't find the right instructions, this is a suggestion for
improving the web site. Since I mentioned several possibilities, I would
appreciate some guidance as to which way you want things to look, and may then
even come up with a patch.
The instructions on the web speak of "Installing GCC", and do not even mention
that they are not version-specific nor for the current release branch. They
also do not point to the install instructions in the tarball. This is
misleading at best.
In particular, the web instructions speak of "old instructions", but refer only
to "really old instructions", not to instructions for previous releases.
Another issue is that the web instructions refer to released versions when
downloading (suggesting that one should install released versions), and at the
same time list prerequisites that are not applicable to any released version.
next prev parent reply other threads:[~2012-07-12 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 17:28 [Bug web/53919] New: " schnetter at gmail dot com
2012-07-10 17:41 ` [Bug web/53919] " redi at gcc dot gnu.org
2012-07-10 18:27 ` schnetter at gmail dot com
2012-07-10 18:36 ` redi at gcc dot gnu.org
2012-07-10 18:46 ` redi at gcc dot gnu.org
2012-07-10 19:05 ` schnetter at gmail dot com
2012-07-11 7:38 ` rguenth at gcc dot gnu.org
2012-07-12 3:25 ` pinskia at gcc dot gnu.org
2012-07-12 14:44 ` schnetter at gmail dot com [this message]
2012-07-12 16:13 ` pinskia at gcc dot gnu.org
2012-07-14 13:50 ` redi at gcc dot gnu.org
2012-07-16 19:14 ` redi at gcc dot gnu.org
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=bug-53919-4-QEUqDRwujF@http.gcc.gnu.org/bugzilla/ \
--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).