public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eljay Love-Jensen <eljay@adobe.com>
To: "Manuel López-Ibáñez" <manuellopezibanez@yahoo.es>
Cc: GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc 3.2
Date: Sun, 24 Feb 2008 10:06:00 -0000	[thread overview]
Message-ID: <C3E67412.1D37%eljay@adobe.com> (raw)
In-Reply-To: <47C0BEAD.9030301@yahoo.es>

Hi Manuel,

> I was surprised to find an ad for non-free software in GNU's gcc-help
> mailing list. I honestly feel offended by your shameless promotion of
> non-free software in this list.

I presume by "non-free" you mean "not open source", since I believe the two
compilers I mentioned are free (as in "cost no money").

In order to build GCC, you need to have a compiler.  One way to build GCC is
to use one of those other compilers to build GCC, which was the context of
the message to use one of those other compilers as the bootstrap compiler
GCC.

I am sorry you are offended by references to non-open source products in
this forum as a means to bootstrap compile GCC.  No slight was intended
towards open-source software developers.

Sincerely,
--Eljay

  parent reply	other threads:[~2008-02-24  7:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 13:28 shakeeb ahmed
2008-02-22 16:04 ` Eljay Love-Jensen
2008-02-24  2:23   ` Manuel López-Ibáñez
2008-02-24  7:09     ` Mihai Donțu
2008-02-24 10:06     ` Eljay Love-Jensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-22  8:27 g++ man pages umapathy
2002-12-22 10:33 ` umapathy
2002-12-22 13:58   ` gcc 3.2 Geoffrey
2002-12-22 18:18     ` Alexander Helm

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=C3E67412.1D37%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=manuellopezibanez@yahoo.es \
    /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).