gcc / gfortran 5.x

gcc / gfortran 5.x

[Hans Horn]

Group,

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?
I'm trying to build a legacy suite of programs that I know builds under 
5.x, but fails miserably under 6.4.

Thanks,
H.


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

Re: gcc / gfortran 5.x

[Yaakov Selkowitz]

[-- Attachment #1.1: Type: text/plain, Size: 526 bytes --]

On 2017-11-26 23:54, Hans Horn wrote:
> 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?

It is no longer supported.

> I'm trying to build a legacy suite of programs that I know builds under
> 5.x, but fails miserably under 6.4.

Then fix the code:

https://gcc.gnu.org/gcc-6/porting_to.html

If this software is shipped in any of the major Linux distributions,
then may will have patches already.

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: gcc / gfortran 5.x

[Keith Christian]

Yaakov,

To help Hans a bit, do we know is the Wayback Machine still working
(I've never used it.)

Or, Hans could keep a gfortran 5.x system around, or roll back the
latest Cygwin updates until he's had a chance to as you say, fix the
code.

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

Re: gcc / gfortran 5.x

[Marco Atzeri]

On 27/11/2017 20:29, Keith Christian wrote:
> Yaakov,
> 
> To help Hans a bit, do we know is the Wayback Machine still working
> (I've never used it.)

http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html


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

Re: gcc / gfortran 5.x

[LMH]

Hans Horn wrote:
> Group,
> 
> 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?
> I'm trying to build a legacy suite of programs that I know builds under 5.x, but
> fails miserably under 6.4.
> 
> Thanks,
> H.
> 
> 
> -- 
> 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
> 
> 

I keep older cygwin installations around to support code that won't compiler on newer
compilers and doesn't use any newer language features. This code often isn't worth
the expenditure to bring up to date. As long as the compiled binaries still run on
current systems, the code won't get updated unless the update is a minor fix.

You can have as many cygwin installations on your system as you want, just name the
root folder and install folder something different for each one. There are potential
problems if you try to run more than one version at the same time. I have had
different answers on this but I don't do it in case there may be problems that aren't
evident.

I start the older cygwin terminals using a .bat file that configures the /cygwin/bin
PATH environment variable for the version of cygwin I are running.

The .bat file looks like,

@echo off

:: remove "C:\cygwin\bin" from PATH
set "PATH=;%PATH%;"
set "PATH=%PATH:;;=;%"
set "PATH=;%PATH:;C:\cygwin\bin;=;%;"
set "PATH=%PATH:;;=%"

:: create a local environment variable for the alternate cygwin version (cygwin2)
set "PATH=C:\cygwin2\bin;%PATH%"
start "" /b C:\cygwin2\bin\mintty.exe -i /Cygwin-Terminal.ico -

I leave this .bat file in the install directory for the alternate cygwin and have a
shortcut on my desktop that runs the bat file. When I want to start an alternate
version of cygwin, I just click on the icon I want. I also have modified the terminal
settings so that the background color of the bash window is different for each
version I have installed. That reminds me of what version of cygwin I am in.

If this is something you really need, like everything else, keep a backup copy of the
cygwin root directory and install directory. The time machine site has worked for me
in the past, but it was very slow. You probably will want to download using wget and
be prepared to leave going it all day.

LMH





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

Re: gcc / gfortran 5.x

[Achim Gratz]

LMH writes:
> You can have as many cygwin installations on your system as you want, just name the
> root folder and install folder something different for each one. There are potential
> problems if you try to run more than one version at the same time.

As long as they don't see each other via PATH or try to run daemons on
the same port you'll have no trouble running them all in parallel.

> I start the older cygwin terminals using a .bat file that configures the /cygwin/bin
> PATH environment variable for the version of cygwin I are running.

Well, I'd rather suggest to modify system settings and create a system
or user variable CYGWIN_NOWINPATH=1.  That keeps the Windows PATH out of
Cygwin entirely, if you need to graft something back that you need, you
can do that in Cygwin by inspecting $ORIGINAL_PATH.  Provide a shortcut
to mintty in each of your Cygwin installations that uses the respective
installation directory as the CWD and have it start a login shell; you
need to use an absolute path, so '/usr/bin/bash -l'.  You might want to
give each shortcut a different foreground/background color in mintty so
you can tell them apart more easily.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
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

Re: gcc / gfortran 5.x

[Achim Gratz]

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

Re: gcc / gfortran 5.x

[Hans Horn]

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