From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Van Ly <van.ly@sdf.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: unreachable intro to gcc page linked to on readings page
Date: Wed, 24 Aug 2022 12:41:43 +0100 [thread overview]
Message-ID: <CAH6eHdTmrjaytXX=S3VMzQepAPtYgS=LwijuJXqnAfFaZO9EMg@mail.gmail.com> (raw)
In-Reply-To: <5c5f8d82-9dd8-1334-2067-d944b77fefc@SDF.ORG>
On Sun, 7 Aug 2022 at 09:33, Van Ly via Gcc <gcc@gcc.gnu.org> wrote:
>
>
> Hello,
>
> On the readings page
>
> . https://gcc.gnu.org/readings.html
>
> a broken link points to
>
> An introduction to GCC by Brian J. Gough.
> . http://www.network-theory.co.uk/gcc/intro/
>
> which has a copy at
>
> . https://web.archive.org/web/20060106062936/http://www.network-theory.co.uk/gcc/intro/
Thanks for letting us know.
There are much more recent archived copies like
https://web.archive.org/web/20181113021321/http://www.network-theory.co.uk/gcc/intro/
I'm not sure it's worth updating the link to an archived copy of that
page, because all the links for buying a PDF or printed copy are
probably dead now anyway.
We could link to https://archive.org/details/B-001-002-835 instead, or
to the archived HTML version. The newest capture of the HTML version
seems to be this, although I didn't check that all pages are archived:
https://web.archive.org/web/20181206025406/http://www.network-theory.co.uk/docs/gccintro/
My preference would be to link to that latter. Although it's quite
dated, the sections on basic compilation and compiler flags are still
relevant for beginners.
Gerald?
next prev parent reply other threads:[~2022-08-24 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 8:33 Van Ly
2022-08-24 11:41 ` Jonathan Wakely [this message]
2022-08-29 10:31 ` Gerald Pfeifer
2022-09-01 11:01 ` [wwwdocs] " Jonathan Wakely
2022-09-21 9:32 ` Jonathan Wakely
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='CAH6eHdTmrjaytXX=S3VMzQepAPtYgS=LwijuJXqnAfFaZO9EMg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=van.ly@sdf.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).