From: Unknown <ashmew2@gmail.com>
To: gcc@gcc.gnu.org
Subject: Broken links for 4.9.4 manuals
Date: Sat, 14 Jan 2017 12:21:00 -0000 [thread overview]
Message-ID: <20170114132112.2f68ba96@h4xX0r-r3b0rn> (raw)
Hi!
I found the official GCC page for manuals[1].
But unfortunately, the libstdc++ docs for my compiler version (4.9.4)
cannot be accessed due to broken links on the webpage.
These are the ones that do not work presently:
GCC-4.9.4 Manuals
- GCC 4.9.4 Standard C++ Library Manual (also in PDF or XML or
an HTML tarball)
- GCC 4.9.4 Standard C++ Library Reference
Manual (also in PDF or XML GPL or XML GDL or an HTML tarball
Please note that none of the PDF/XML/Tarball/others work.
Could someone fix them up?
Thanks!
Ashish Gupta
--
Sent to this mailing list because of this site footer on [1]:
For questions related to the use of GCC, please consult these web pages
and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing
list might help. Comments on these web pages and the development of GCC
are welcome on our developer list at gcc@gcc.gnu.org. All of our lists
have public archives.
[1] : https://gcc.gnu.org/onlinedocs/
next reply other threads:[~2017-01-14 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 12:21 Unknown [this message]
2017-01-15 1:24 ` Jonathan Wakely
2017-01-15 12:50 ` Jonathan Wakely
2017-01-15 16:50 ` Ashish Gupta
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=20170114132112.2f68ba96@h4xX0r-r3b0rn \
--to=ashmew2@gmail.com \
--cc=gcc@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).