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:29:00 -0000	[thread overview]
Message-ID: <02703004-3392-428D-8E0F-3ACC6F751B40@etr-usa.com> (raw)
In-Reply-To: <CAPCR6Q2PTK_K2Ueg=mdpv8D6Ercwsv=oUTsMf36ss3pfA7E1Wg@mail.gmail.com>

On Mar 23, 2016, at 10:20 PM, Rashi Singhal <singhal.rashi@gmail.com> wrote:
> 
> Is there any other procedure for building an older release of cygwin.

Cygwin is not GCC Ada, nor vice versa.

I’m being pedantic because you’re referencing Cygwin build instructions but having trouble with a third-party package.  You may have the version of GCC Ada that was distributed at the same time that Cygwin 1.7.0-58 was current, but that doesn’t mean that version of Cygwin’s build instructions are relevant to GCC Ada.

You need to read the README and INSTALL files that came with GCC Ada.

I’ve never built GCC Ada from source — or used it as a binary, for that matter — but I’ll go through your config.log file and see what I can see.

> Invocation command line was
> 
>   $ /oss/src/configure --prefix=/oss/install -v

That seems very odd.

First, it implies that you have unpacked the Cygwin GCC Ada source package into /oss/src.  It should be unpacked into a directory named gcc-ada-*, shouldn’t it?

Second, running a GNU autoconf configure script from a directory other than the source tree means you get a separate build tree.  GCC Ada should be able to be built that way, but usually the pattern looks different from what you show.  That implies that you haven’t read the GCC Ada build instructions.

> uname -v = 2009-08-13 17:52

Well, that’s a good sign.  It implies that you have gotten Cygwin 1.7.0-58 built and are building underneath it.  Are you using a contemporaneous version of all the other tools?  Shell, make, gcc, newlib, libbfd, etc.?

What I’m getting at is, by this point you should have a standalone basic Cygwin 1.7 environment, no longer dependent on any Cygwin 2.x DLLs, tools, etc.  Do you?

> configure:3288: gcc --version </dev/null >&5
> gcc (GCC) 4.3.2 20080827 (beta) 2
> Copyright (C) 2008 Free Software Foundation, Inc.

It looks like you don’t have a standalone environment yet.

According to the Cygwin Time Machine, Cygwin was still shipping GCC 3.4.4 at that time.

Which reminds me: why are you building from source and not using the binaries from the Cygwin Time Machine?

Even if you want to build from source eventually, you should rebuild everything using contemporaneous tools, not modern ones.

> configure:4175: g++ -c -g -O2  conftest.cc >&5
> conftest.cc:9: error: 'void std::exit(int)' should have been declared inside 'std'
> In file included from conftest.cc:10:
> /usr/include/stdlib.h:80: error: declaration of 'void std::exit(int)' throws different exceptions
> conftest.cc:9: error: from previous declaration 'void std::exit(int) throw ()'
> configure:4181: $? = 1
> 

That’s the sort of error you get when trying to build old (7 years!) sources with current tools.
--
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:29 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 [this message]
2016-03-24 19:36                         ` Warren Young
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=02703004-3392-428D-8E0F-3ACC6F751B40@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).