public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "John (Eljay) Love-Jensen" <eljay@adobe.com>
To: Robert Jones <robertgbjones@gmail.com>,
	        "gcc-help@gcc.gnu.org" 	<gcc-help@gcc.gnu.org>
Subject: RE: g++ versions
Date: Wed, 11 Feb 2009 13:37:00 -0000	[thread overview]
Message-ID: <204DEA5423F3BF47A6EE88C4E2979EC66BE32F035F@nambx04.corp.adobe.com> (raw)
In-Reply-To: <4efd67eb0902110513j323585d1s8a6e1899647f00ca@mail.gmail.com>

Hi Rob,

Using Cygwin SETUP.EXE, the GCC that is available from that installer is the latest GCC that works on Cygwin.

There are several issues in trying to get the latest GCC up-and-running under Cygwin.

I read the issues a while back, but did not note exactly what they were, or the URL that enumerated the issues.  [Sorry.  Hopefully someone a little closer to the problem can cite both.  Or dig around in the gcc-help archives.]

There are several people working on getting the latest GCC working properly (i.e., no surprises when you compile and run your code) on Cygwin.  Since there have been several releases of GCC since 3.4, I think that is indicative that the "get GCC working on Cygwin" problem is hard.

I do not know if the GCC problems with Cygwin are the same with MinGW's GCC.  (I see MinGW has a GCC 4.3 available, but it is tagged as "testing".  MinGW 5.1.3 installer looks like it comes with GCC 3.4 as stock.)

Sincerely,
--Eljay

  reply	other threads:[~2009-02-11 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 13:13 Robert Jones
2009-02-11 13:37 ` John (Eljay) Love-Jensen [this message]
2009-02-11 14:22   ` Robert Jones
2009-02-11 14:31 ` Tim Prince
2009-02-11 15:30   ` Robert Jones
2009-02-11 16:34     ` David Gressett
2009-02-11 17:03     ` Tim Prince

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=204DEA5423F3BF47A6EE88C4E2979EC66BE32F035F@nambx04.corp.adobe.com \
    --to=eljay@adobe.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=robertgbjones@gmail.com \
    /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).