DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Ut5vkXASktuZa6hQaH1Z5ZFaiUCmrk33LPEnv2o7q7B
	q4ECN3crZxsyEtJmkYePNa2z17W4OlJJuRUbl3p3Qv7ahUexpuVkEzFCwOL4DSiZ
	whF7dKnQcYoluwmpXjyutZHtZs62QqrJhzFf0wFdDy84ZaiykKSCsUFIrmqea+BU
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <52FB0686.8080403@gmail.com>
Date: Wed, 12 Feb 2014 06:28:38 +0100
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: g77 on cygwin64
References: <52FAF082 DOT 6020805 AT appstate DOT edu>
In-Reply-To: <52FAF082.6020805@appstate.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 12/02/2014 04:54, Scott T. Marshall wrote:
> Hi All,
> First a compliment: I recently went from the old x86 version of cygwin
> to cygwin64. I was pleased to see that many of my perl scripts run about
> twice as fast. Thanks!
>
> My question: Would it be possible to have the old g77 fortran compiler
> as an optional install for cygwin64? I realize that g77 is now
> deprecated by gfortran, but I have a lot of old fortran 77 code that
> does not compile correctly with gfortran. Since I am not a fortran coder
> (I mainly use interpreted languages), I do not have the skills to figure
> out what the issues with gfortran are. It would immensely useful to have
> a cygwin64 g77 as an optional install.
>
> If this is not an option, could anyone maybe point me in the right
> direction as to how to compile g77 myself? I attempted to do so with an
> old g77 from gcc version 3.4.6, but the makefiles do not recognize the
> uname of cygwin64, and I'm not sure of what compiler flags to use, so
> the build always fails.
>
> Any tips/suggestions would be appreciated.
> Cheers,
> -Scott
>

have you tested with -std=legacy ?

'-std=STD'
      Specify the standard to which the program is expected to conform,
      which may be one of 'f95', 'f2003', 'f2008', 'gnu', or 'legacy'.
      The default value for STD is 'gnu', which specifies a superset of
      the Fortran 95 standard that includes all of the extensions
      supported by GNU Fortran, although warnings will be given for
      obsolete extensions not recommended for use in new code.  The
      'legacy' value is equivalent but without the warnings for obsolete
      extensions, and may be useful for old non-standard programs.  The
      'f95', 'f2003' and 'f2008' values specify strict conformance to the
      Fortran 95, Fortran 2003 and Fortran 2008 standards, respectively;
      errors are given for all extensions beyond the relevant language
      standard, and warnings are given for the Fortran 77 features that
      are permitted but obsolescent in later standards.  '-std=f2008ts'
      allows the Fortran 2008 standard including the additions of the
      Technical Specification (TS) 29113 on Further Interoperability of
      Fortran with C.


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