public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin 1.7-58 with windows 2008
Date: Thu, 24 Mar 2016 19:36:00 -0000	[thread overview]
Message-ID: <9E004C43-80A0-4297-BD2C-BC858BC4738F@etr-usa.com> (raw)
In-Reply-To: <02703004-3392-428D-8E0F-3ACC6F751B40@etr-usa.com>

On Mar 24, 2016, at 1:29 PM, Warren Young <wyml@etr-usa.com> wrote:
> 
> On Mar 23, 2016, at 10:20 PM, Rashi Singhal <singhal.rashi@gmail.com> wrote:
>> 
>> configure:3288: gcc --version </dev/null >&5
>> gcc (GCC) 4.3.2 20080827 (beta) 2
>> Copyright (C) 2008 Free Software Foundation, Inc.
> 
> According to the Cygwin Time Machine, Cygwin was still shipping GCC 3.4.4 at that time.

Ooops, never mind.  I now see that Cygwin was still shipping two different versions of GCC back then, and its gcc4 is 4.3.2.

Still, I think I’m still correct about the core diagnosis for the std::exit() thing the GCC Ada configure script is complaining about, except that it’s a too-new C++ Standard Library causing the problem, rather than a too-new C++ compiler.

Or, I could still be right, since you claim to have downloaded “gcc-ada” rather than “gcc4-ada”.  If that’s literally what you’ve done, you should be building with GCC 3, not GCC 4.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-03-24 19:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  8:44 Rashi Singhal
2016-02-17  9:09 ` Marco Atzeri
2016-02-22  9:50 ` Rashi Singhal
2016-02-22 11:21   ` Marco Atzeri
2016-02-23  3:34   ` Rashi Singhal
2016-02-23 14:01     ` Marco Atzeri
2016-03-04 16:40     ` Rashi Singhal
2016-03-09  8:00       ` Rashi Singhal
2016-03-09  8:16         ` Marco Atzeri
     [not found]         ` <CAPCR6Q2GdXd=EF7iAdP+xYT7UomLefLKgDm=be0oD=Wh64T_-g@mail.gmail.com>
2016-03-11  2:40           ` Rashi Singhal
2016-03-11  6:38             ` Mark Geisert
2016-03-17 11:19             ` Rashi Singhal
2016-03-17 11:47               ` Marco Atzeri
2016-03-18 16:15               ` Peter A. Castro
     [not found]                 ` <CAPCR6Q32VQeQLLjOC6t5UNs-AVtHYC_Er1ETdZHtYifbD6j3rA@mail.gmail.com>
     [not found]                   ` <alpine.LNX.2.00.1603231447150.6583@ming.fruitbat.org>
2016-03-24  4:20                     ` Fwd: " Rashi Singhal
2016-03-24 19:29                       ` Warren Young
2016-03-24 19:36                         ` Warren Young [this message]
2016-03-25  5:38                       ` Fwd: " Mark Geisert
2016-03-28  9:08                       ` Rashi Singhal
2016-03-28 10:50                         ` Andrey Repin
2016-03-28 11:06                           ` Rashi Singhal
2016-03-28 14:30                             ` Erik Soderquist
2016-03-29  2:47                       ` Rashi Singhal
  -- strict thread matches above, loose matches on Subject: below --
2016-02-17  5:53 Rashi Singhal
2016-02-17  6:50 ` Larry Hall (Cygwin)

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=9E004C43-80A0-4297-BD2C-BC858BC4738F@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin@cygwin.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).