public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@mengyan1223.wang>
To: "DeCaro,
	James John (Jim) CIV DISA FE (USA)"
	<james.j.decaro3.civ@mail.mil>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Installing gcc on Linux 7.9 with no access to a repository
Date: Tue, 03 May 2022 20:32:54 +0800	[thread overview]
Message-ID: <ced38a2f2ee8ad9323b0560ab0e8dd47f2d55c56.camel@mengyan1223.wang> (raw)
In-Reply-To: <SN5P111MB118178B75BAD7C102CD9C55AD0C09@SN5P111MB1181.NAMP111.PROD.OUTLOOK.COM>

On Tue, 2022-05-03 at 12:18 +0000, DeCaro, James John (Jim) CIV DISA FE
(USA) wrote:
> I am trying to download and install gcc manually, since I do not have
> access to a repository.  When I try to run  ./configure from the gcc
> download I get a message that there is no compiler available (--well
> OK, this is what I am trying to fix).  I am having difficulty finding
> a simple compiler download that will install without the benefit of
> access to a repository.  I tried downloading .rpm’s to install locally
> but with no luck so far.

What is "Linux 7.9"?  The latest release of Linux is 5.18.

-- 
Xi Ruoyao <xry111@mengyan1223.wang>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-05-03 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 12:18 DeCaro, James John (Jim) CIV DISA FE (USA)
2022-05-03 12:32 ` Xi Ruoyao [this message]
2022-05-03 13:05   ` [Non-DoD Source] " DeCaro, James John (Jim) CIV DISA FE (USA)
2022-05-03 15:37     ` Jonathan Wakely
2022-05-03 17:43       ` DeCaro, James John (Jim) CIV DISA FE (USA)
2022-05-03 18:49         ` Jonathan Wakely
2022-05-03 19:00           ` [URL Verdict: Neutral]Re: " DeCaro, James John (Jim) CIV DISA FE (USA)

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=ced38a2f2ee8ad9323b0560ab0e8dd47f2d55c56.camel@mengyan1223.wang \
    --to=xry111@mengyan1223.wang \
    --cc=gcc-help@gcc.gnu.org \
    --cc=james.j.decaro3.civ@mail.mil \
    /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).