X-Recipient:	archive-cygwin AT delorie DOT com
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=XYUc4GGtKJQeHkrVKwFCQLPXUI217FVotJni4lEzIF+
	ftRYYj9UfAx5ahc/LKb1XeeMLUEMu3tfSRgScA+zL7U/YtY7Jq3wrQb2/jY2VS5U
	JxxFIipccWzIlfTB49+21GrL1EFhPi8sYgB6vXuEVSB04mnwqfEK1xZLlYoTK2D4
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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;
	s=default; bh=w40YRxEurs4rt42O963WA7PSdpY=; b=kfhZ8zrkjLepCWVKR
	pxzGvs1SIheH29hGXDTdyfAgTBhhaEci2xxnW49UnC3RUEpox25bSshZ7Dtj4Pzg
	Fk4dQyFzfdySpg/wmovn49FmpCvykja3EnxYUiO/BMvlVb/yoNFilE7EsnzTFdg2
	nnGFlPlmknMvnBP4szGjgxRzmM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	mta7.appstate.edu
Message-ID:	<52FB13E2.1070107@appstate.edu>
Date:	Wed, 12 Feb 2014 01:25:38 -0500
From:	"Scott T. Marshall" <marshallst AT appstate DOT edu>
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> <52FB0686 DOT 8080403 AT gmail DOT com>
In-Reply-To:	<52FB0686.8080403@gmail.com>
X-MailScanner-Information:	Please contact the Helpdesk @ 6266 for more information
X-Appstate-MailScanner-ID:	s1C6Pcjg030042
X-MailScanner-ASU-mta:	Found to be clean
X-MailScanner-SpamCheck:	not spam, SpamAssassin (not cached, score=-2.75, required 5, autolearn=disabled, ALL_TRUSTED -1.00, APPSTATE_ALLOW_APPSTATE -1.75)
X-IsSubscribed:	yes

On 2/12/2014 12:28 AM, Marco Atzeri wrote:
>
>
> 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.
>
Yup, I tried that compiler flag (-std=legacy) with gfortran. No luck. 
Back when cygwin was x86 only and had g77, the same code compiled 
correctly and ran fine. I have the same issues on Linux boxes, so the 
gfortran issue is not unique to cygwin. The solution I found was to dig 
up the old binaries for my Linux boxes and install g77 on them. I don't 
think I can do this for cygwin since g77 was never a part of cygwin64. 
Would it be very difficult to take the old g77 source and recompile it 
for cygwin64? Has anyone successfully done this before?
Cheers
-Scott

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


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

- Raw text -