From: "Bras, Gerard via RT" <info@fsf.org>
To: maurice_mukuna@yahoo.fr
Cc: gcc-help@gcc.gnu.org,gnu@gnu.org,steve@smc.vnet.net
Subject: RE: [gnu.org #211945] I need your help !
Date: Tue, 12 Oct 2004 17:21:00 -0000 [thread overview]
Message-ID: <rt-3.0.8-211945-662758.11.4928250117723@rt.gnu.org> (raw)
In-Reply-To: <rt-211945@gnu.org>
John,
This is a little off topic for this list, but WTF....
> gunzip: gcc-3.3.2-sol8-sparc-local.gz: unexpected end of file
One of several things happened. In decreasing order of likelihood:
1) Your download failed at your end. Either you did ASCII mode after all, or you ran out of disk space, or your FTP client timed out prematurely, or.... Check the size of the file you ended up with against what's on the server.
2) The file is broken on the server. It happens. If you are sure you got a clean download and it's still won't get through gunzip, try to downloading it form somewhere else.
cheers,
Gerard
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]On
Behalf Of John Sullivan via RT
Sent: Tuesday, October 12, 2004 12:26 PM
To: maurice_mukuna@yahoo.fr
Cc: gcc-help@gcc.gnu.org; gnu@gnu.org; steve@smc.vnet.net
Subject: Re: [gnu.org #211945] I need your help !
> Hi,
>
> i'm software analyst and developer in Belgium.
> I want to test and compare the performance of some JVM and compilers (JIT, Native code generator, JVM Optimised).
> I'm facing some problème when installing GCJ.
> I want to install GCJ on Solaris Sparc 64 plateform.
> When i transfert "gcc-3.3.2-sol8-sparc-local.gz" file (with or without binary FTP command) and i gunzip it, i have the following error :
> bash-2.03$ gunzip gcc-3.3.2-sol8-sparc-local.gz
> gunzip: gcc-3.3.2-sol8-sparc-local.gz: unexpected end of file
>
> What about this file and where i can find the good one ?
> Where i can find good articles ?
> There is two days i'm stopped.
>
Hello,
I'm sorry, but as this is only a general contact address, I cannot
properly answer technical questions such as yours. The best I can do is
refer you to the GCC Manual (http://gcc.gnu.org/onlinedocs/) and Frequently
Asked Questions (http://gcc.gnu.org/faq.html). If neither of those provide
an answer to your question, please contact the GCC users' help list; you
can learn more about it at <http://gcc.gnu.org/lists.html>.
I am sorry that I couldn't be of more help.
--
Sincerely,
John Sullivan
Program Administrator
Free Software Foundation Phone: (617)542-5942 x23
59 Temple Place, Suite 330 Fax: (617)542-2652
Boston, MA 02111-1307 USA Email: info@fsf.org
http://member.fsf.org
next prev parent reply other threads:[~2004-10-12 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rt-211945@gnu.org>
2004-10-12 16:23 ` John Sullivan via RT
2004-10-12 17:21 ` Bras, Gerard via RT [this message]
2004-10-12 17:24 ` Bras, Gerard via RT
2004-10-12 17:31 ` lrtaylor@micron.com via RT
2004-10-12 17:32 ` lrtaylor@micron.com via RT
2004-10-13 8:27 ` steve@smc.vnet.net via RT
2004-10-13 8:27 ` steve@smc.vnet.net via RT
2004-10-13 8:27 Steven M. Christensen
-- strict thread matches above, loose matches on Subject: below --
2004-10-12 17:30 lrtaylor
2004-10-12 17:21 Bras, Gerard
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=rt-3.0.8-211945-662758.11.4928250117723@rt.gnu.org \
--to=info@fsf.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gnu@gnu.org \
--cc=maurice_mukuna@yahoo.fr \
--cc=steve@smc.vnet.net \
/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).