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=kmk0zWTOlARxGj/Gd1K+cZmfi/GmHv1V0SLpIIfJxt4
	o6ZtOxNYN7VADbf+5UOufgb3sB93jcd3ZMZ8WR7waQE3N4gCodpEldAuXIqQP9Uu
	1/irKF6B+Tibgs/Gt+ld0Amusp+V0ZnxYjFEAFv+quduKiy10FaQXBRlm6mayjfA
	=
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=1FErSHHnXgB+xxem8Q6DIzDkoQ4=; b=RD/+2pNWen7YDV69C
	B8BNqnjvNEc0vSTtvOVQJL5O1z+LxbCOUCrH/xACI14IP5yVq39F27FDgghNLe7d
	d+ucyjnoy/BjhS1e35gk6uovQfhK5Ej3k6gJjxjpWXDRKCoaOpVSIP0OtFBgj1sl
	PW0FMk55XLqt8DNmpfNKKfsCWM=
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=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	smtp107.biz.mail.ne1.yahoo.com
X-Yahoo-SMTP:	ycweUreswBCK.d0cygTP5tXwHncbOU7YVeVfIxOQoyRMI2IuIKLmUqE-
X-Rocket-Received:	from [192.168.10.27] (lmh_users-groups AT 76 DOT 119 DOT 36 DOT 62 with plain [98.138.105.25]) by smtp107.biz.mail.ne1.yahoo.com with SMTP; 11 Feb 2014 23:23:56 -0800 PST
Message-ID:	<52FB2186.3030606@molconn.com>
Date:	Wed, 12 Feb 2014 02:23:50 -0500
From:	LMH <lmh_users-groups AT molconn DOT com>
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23
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> <52FB13E2 DOT 1070107 AT appstate DOT edu>
In-Reply-To:	<52FB13E2.1070107@appstate.edu>
X-IsSubscribed:	yes

What host operating system are you running cygwin on? Do you have 
examples of your old g77 applications that are already compiled that you 
can test on your current system?

There are several options. Compiling g77 is one of them, but you would 
need the proper runtime components as well. It is also possible to have 
more than one cygwin installation. You can have an older x86 cygwin 
installed that still has g77. The question is weather or not an app 
compiled with g77 under 32-bit cygwin will run on your OS. You also 
would not be able to run both versions of cygwin at the same time.

A think a bit more information would be useful.

This is the gnu archive page for gcc version 3.4.6, which I think is the 
one that is most compatible with the gcc 4 stuff.

http://ftp.gnu.org/gnu/gcc/gcc-3.4.6/

If I remember right, you could not compile with 3.4.4 once your cygwin 
had been updated to gcc 4. There were some collisions and header issues. 
I think that had been fixed by 3.4.6, but cygwin had moved on from gcc 3 
by then and they never released a package past 3.4.4.

I think you can get it compiled and it would probably be better to 
consult with the gnu message board about that, since that's there thing. 
If you think it would be useful to try installing a second cygwin, I can 
send you some notes for that.

LMH


Scott T. Marshall wrote:
>
> 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
>
>

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