X-Spam-Check-By: sourceware.org
Message-ID: <108fc8470606271420k6627e72bkaddb68c1d38515dd@mail.gmail.com>
Date: Tue, 27 Jun 2006 17:20:05 -0400
From: "Brad Krane" <brad DOT krane AT gmail DOT com>
To: "Cygwin General List" <cygwin AT cygwin DOT com>
Subject: Re: Fortran Compiler Error CMBFAST
In-Reply-To: <4C89134832705D4D85A6CD2EBF38AE0F549723@PAUMAILU03.ags.agere.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <449F7983 DOT 7000606 AT sbcglobal DOT net> 	 <4C89134832705D4D85A6CD2EBF38AE0F549723 AT PAUMAILU03 DOT ags DOT agere DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Yes I forgot to mention that the include file that the compiler could
not find was in the working directory.

Adding a -I./ to the flags has seemed to solve this.

On 6/26/06, Williams, Gerald S (Jerry) <gsw AT agere DOT com> wrote:
> Brad Krane wrote:
> > I'm trying to compile the scientific package CMBFAST-4.5.1 in the
> > cygwin environment using g77. I get the following error...
> >
> > f77 -O2   -c -o jlgen.o jlgen.F
> > jlgen.F: In program `jlgen':
> > jlgen.F:14:
> >         include 'cmbfast.inc'
> >         ^
> > Unable to open INCLUDE file `cmbfast.inc' at (^)
>
> Tim Prince wrote:
> > Normally, you would specify the path to search for include files with
> > -I, if it is not in the current working directory.
>
> I looked at the library, and the referenced include file
> *is* in the same directory. The library even includes a
> configure script, so this isn't simple pilot error--it
> looks like there is a bug in the compiler.
>
> For now, you can work around the problem by adding -I. to
> the command lines, or more likely to the end of FFLAGS in
> the Makefile (after running ./configure).
>
> I don't use FORTRAN enough to say whether the behavior we
> are seeing is correct, though from the evidence I've seen
> I'd say it isn't.
>
> gsw
>


-- 
Brad

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/