From: David Edelsohn <dje@watson.ibm.com>
To: Darin DeCounter <ddecounter@reviewjournal.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Help! Attempting to install gcc 3.0.4
Date: Mon, 06 May 2002 09:43:00 -0000 [thread overview]
Message-ID: <200205061642.MAA21838@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Darin DeCounter <ddecounter@reviewjournal.com> of "Mon, 06 May 2002 08:33:42 PDT." <3.0.6.32.20020506083342.007aa100@dali.lvrj.com>
>>>>> Darin DeCounter writes:
Darin> Ok, so when they say GCC needs to be 'built', the binary distribution is
Darin> pre-built? I didn't know that's what this refers to. The 'source' tar
Darin> file is what had the 'configure' file in the top-directory. I had the
Darin> 'executable' tar file even before that, but it wasn't a .bin file. I'll go
Darin> back to UCLA's site and see if I can find the binary, because if I can
Darin> install via SMIT this sounds like what I want. Thank you.
The binary distribution is pre-built, meaning that it has been
configured and compiled for AIX. It should be a snapshot of the files
installed by GCC so that it can be installed on another system.
I believe that UCLA repository distributes tar files and the
Groupe Bull repository distributes AIX installp-format (SMIT) files. UCLA
also mirrors the Groupe Bull website with a link at the bottom-left side
column on the UCLA welcome page.
David
next parent reply other threads:[~2002-05-06 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.6.32.20020506083342.007aa100@dali.lvrj.com>
2002-05-06 9:43 ` David Edelsohn [this message]
[not found] <3.0.6.32.20020506105356.007a7d00@dali.lvrj.com>
2002-05-06 11:09 ` David Edelsohn
[not found] <3.0.6.32.20020506104130.007ad720@dali.lvrj.com>
2002-05-06 10:48 ` David Edelsohn
[not found] <3.0.6.32.20020506081536.007a3e50@dali.lvrj.com>
2002-05-06 8:18 ` David Edelsohn
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=200205061642.MAA21838@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=ddecounter@reviewjournal.com \
--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).