From: Andrew Cannon <ajc@gmx.net>
To: gcc-help@gcc.gnu.org
Subject: Re: Looking for old release sources
Date: Tue, 10 Oct 2000 01:55:00 -0000 [thread overview]
Message-ID: <39E2D99C.B3261240@gmx.net> (raw)
In-Reply-To: <orsnq5qooh.fsf@guarana.lsd.ic.unicamp.br>
Ah, thanks. That allows me to get 2.6.2 by reverse patching from
2.7.2.1.
But there's still no way to get to 2.3.3 from either side. The patches
stop after 2.3.3 and continue with 2.4.0....!
Has anyone out there got copies of the older releases that are missing
from the ftp server?
Andrew
Alexandre Oliva wrote:
>
> On Oct 8, 2000, Andrew Cannon <ajc@gmx.net> wrote:
>
> > I need to get the source tarballs for releases 2.3.3 and 2.6.2 of gcc,
> > but the gnu ftp sites and mirrors only have patches to generate these
> > from earlier releases.
>
> Get newer releases and use patch -R.
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist *Please* write to mailing lists, not to me
prev parent reply other threads:[~2000-10-10 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-08 3:17 Andrew Cannon
2000-10-09 21:57 ` Alexandre Oliva
2000-10-10 1:55 ` Andrew Cannon [this message]
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=39E2D99C.B3261240@gmx.net \
--to=ajc@gmx.net \
--cc=gcc-help@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).