[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: netCDF Fortran (77 + 90) - Failed to find lahey fortran/failed build 3.6.1

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: netCDF Fortran (77 + 90) - Failed to find lahey fortran/failed build 3.6.1
  • Date: Fri, 28 Oct 2005 07:24:33 -0600
"Rochelle Labiosa" <address@hidden> writes:

> Institution: Stanford University
> Package Version: netcdf 3.6.1_beta3
> Operating System: CYGWIN, Windows XP
> Hardware Information: Dell Pentium PC 2.52 Ghz processor
> Inquiry: I sent an email earlier today, and this is a follow up. I was having 
> trouble with unresolved external symbols when using the prebuilt netcdf dll 
> with lahey fujitsu fortran 95 using CYGWIN (everything is in my path, plus 
> the libraries are linked properly). I figured it could be a CYGWIN problem, 
> so I decided to compile the components myself, and I picked the build 3.6.1 
> beta3, as it is supposed to have a CYGWIN bug fix. However, in the config.log 
> (build failed for fortran), I noticed something interesting--it tried to call 
> f95.exe and received a serializiation error when trying to link with fortran. 
> Although f95.exe exists in my lahey-fujitsu bin directory, the correct 
> executable is lf95.exe, located in the same directory. Is there any way to 
> correct this problem?
>
> Cheers,
> Rochelle
>
> attached: config.log
>
>

Before you do the configure, set environmental vars F95 and F77 to
lf95, like this:

F95=lf95 F77=lf95 ./configure

Let me know if this doesn't work.

Ed
-- 
Ed Hartnett  -- address@hidden