From: "Mcfall, Troy D" <troy.mcfall@eds.com>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Problem
Date: Wed, 01 Sep 1999 16:22:00 -0000 [thread overview]
Message-ID: <D201FAA966D9D211826E00805F313CC898BAFD@USSAM201> (raw)
The file gcc-core-2_95_1_tar.gz on the stanford download seems to get an
error when unzipping. I tried one of the other sites and it worked fine....
Troy McFall
916-861-3280
WARNING: multiple messages have this Message-ID
From: "Mcfall, Troy D" <troy.mcfall@eds.com>
To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
Subject: Problem
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <D201FAA966D9D211826E00805F313CC898BAFD@USSAM201> (raw)
Message-ID: <19990930180200.peUX43FZ5BiOMMoUmQ7CCizjZ6Ou-zywNosGfnWAo6Q@z> (raw)
The file gcc-core-2_95_1_tar.gz on the stanford download seems to get an
error when unzipping. I tried one of the other sites and it worked fine....
Troy McFall
916-861-3280
next reply other threads:[~1999-09-01 16:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 16:22 Mcfall, Troy D [this message]
1999-09-01 22:04 ` Problem Jeffrey A Law
1999-09-30 18:02 ` Problem Jeffrey A Law
1999-09-30 18:02 ` Problem Mcfall, Troy D
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 22:19 problem Virender Kashyap
2005-02-15 21:27 ` problem James E Wilson
2001-12-19 9:48 problem GTFSTBK
2001-12-19 3:14 problem dewar
[not found] <616BE6A276E3714788D2AC35C40CD18D29DBF7@whale.softwire.co.uk>
2001-12-19 1:42 ` problem Rupert Wood
[not found] <616BE6A276E3714788D2AC35C40CD18D29DBCF@whale.softwire.co.uk>
2001-12-18 23:54 ` problem Rupert Wood
2001-12-19 0:04 ` problem Russ Allbery
2001-12-19 8:47 ` problem Tim Prince
2001-12-18 23:40 problem GTFSTBK
2001-10-19 8:14 problem Nurse, Brian
2001-10-19 8:37 ` problem Phil Edwards
1999-10-10 9:47 problem Florin Iucha
1999-10-31 23:35 ` problem Florin Iucha
1999-10-09 13:49 problem Nathan A. Feger
1999-10-31 23:35 ` problem Nathan A. Feger
1997-10-31 12:08 problem Mike Stump
1997-10-30 19:04 problem Mike Stump
1997-10-30 19:16 ` problem Joe Buck
1997-10-31 11:20 ` problem Jim Wilson
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=D201FAA966D9D211826E00805F313CC898BAFD@USSAM201 \
--to=troy.mcfall@eds.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).