public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hans Horn <hannes@2horns.com>
To: cygwin@cygwin.com
Subject: Re: gcc / gfortran 5.x
Date: Mon, 04 Dec 2017 16:05:00 -0000	[thread overview]
Message-ID: <p03rn2$8fq$1@blaine.gmane.org> (raw)
In-Reply-To: <87y3mrv3q6.fsf@Rainer.invalid>

Thanks to all the lead me the way.
Using cygwin's time machine I was able to build a working cygwin 
enviroment with gcc/gfortran at version 5.40. 
(http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/64bit/2017/09/05/224214/) 


On 11/27/2017 12:58 PM, Achim Gratz wrote:
> Hans Horn writes:
>> I noticed that cywgin's gcc/gfortran has moved whole sale to gcc 6.4.
>> How can I get the latest release of the 5.x branch (32 and 64bit)
>> back?
> 
> Use the Cygwin Time Machine, some other post had the link.
> 
>> I'm trying to build a legacy suite of programs that I know builds
>> under 5.x, but fails miserably under 6.4.
> 
> Been there, done that.  In general, trying to freeze the compilation
> environment is a losing proposition and it's better to fix up the
> sources instead.
> 
> 
> Regards,
> Achim.
> 



--
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:[~2017-12-04 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  5:52 Hans Horn
2017-11-27  6:47 ` Yaakov Selkowitz
2017-11-27 19:29   ` Keith Christian
2017-11-27 20:09     ` Marco Atzeri
2017-11-27 20:11 ` LMH
2017-11-27 20:30   ` Achim Gratz
2017-11-27 20:58 ` Achim Gratz
2017-12-04 16:05   ` Hans Horn [this message]

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='p03rn2$8fq$1@blaine.gmane.org' \
    --to=hannes@2horns.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).