public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Nettles-Moran,
	Kristen K CIV USN NIWC ATLANTIC SC (USA)"
	<kristen.nettles-mora@navy.mil>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: GCC 4.9.2
Date: Thu, 6 Aug 2020 12:03:20 -0700	[thread overview]
Message-ID: <CAKOQZ8zzagyU00tA9Re-+Yzy4BfBB=o1mJfjftbOC+W8QKJ+nQ@mail.gmail.com> (raw)
In-Reply-To: <SN5P111MB0400EFFDC6D9DB661B71637DA3480@SN5P111MB0400.NAMP111.PROD.OUTLOOK.COM>

No license is required to install GCC.  It is free software.  Just
download it and use it.

Ian

On Thu, Aug 6, 2020 at 10:58 AM Nettles-Moran, Kristen K CIV USN NIWC
ATLANTIC SC (USA) <kristen.nettles-mora@navy.mil> wrote:
>
> Good Afternoon,
>
>
>
> We have a requirement for one of our contractors to install the below
> software for testing.  How do we obtain permission for them to obtain/use 6
> licenses?
>
>
>
>
> item
>
> Third party item
>
> elements
>
> type
>
> vendor
>
> provided to Navy 4/30/2020
>
> Mini-Suite
> total licenses needed
>
>
> GNU Compiler Collection (GCC) Runtime libraries
>
> gcc (GCC) 4.9.2 (ALL)- 32 bit
>
> all
>
> FOSS
>
> GNU.org
>
> yes
>
> 6
>
>
>
> I appreciate the assistance in this matter.
>
>
>
> Thank you,
>
>
>
> Kristen
>
>
>
>
>
> **Please add delivery and read receipts to all replies**
>
>
>
> Respectfully,
>
> Kristen Nettles-Moran
>
> NIWC Atlantic Code 62100
>
> Desk: 843-218-4624
>
> DSN: 588-4624
>
> Cell - 1-843-901-3189
>
> NIPR: kristen.nettles-mora@navy.mil
>
> SIPR: kristen.nettles-mora@navy.smil.mil
>
>
>
>
>

  reply	other threads:[~2020-08-06 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 17:57 Nettles-Moran, Kristen K CIV USN NIWC ATLANTIC SC (USA)
2020-08-06 19:03 ` Ian Lance Taylor [this message]
2020-08-06 19:05   ` [Non-DoD Source] " Nettles-Moran, Kristen K CIV USN NIWC ATLANTIC SC (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='CAKOQZ8zzagyU00tA9Re-+Yzy4BfBB=o1mJfjftbOC+W8QKJ+nQ@mail.gmail.com' \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kristen.nettles-mora@navy.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).