public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: gcc / gfortran 5.x
Date: Mon, 27 Nov 2017 20:58:00 -0000	[thread overview]
Message-ID: <87y3mrv3q6.fsf@Rainer.invalid> (raw)
In-Reply-To: <ovg959$jd1$1@blaine.gmane.org> (Hans Horn's message of "Sun, 26	Nov 2017 21:54:33 -0800")

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.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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

  parent reply	other threads:[~2017-11-27 20:58 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 [this message]
2017-12-04 16:05   ` Hans Horn

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=87y3mrv3q6.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).