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

[netCDF #GDO-757215]: netcdf-fortran-4.2 make check install fail



Hi Julia,

> I am working on Windows 7 and successfully installed netcdf-4.2 under
> cygwin. Now I try to install netcdf-fortran-4.2. Configure went alright, but
> when doing make check install I get following error:
> 
> 
> 
> Makefile:732: recipe for target `nf_test.exe' failed
> 
> make[2]: *** [nf_test.exe] Error 1
> 
> make[2]: Leaving directory `/cygdrive/c/build/netcdf-fortran-4.2/nf_test'
> 
> Makefile:989: recipe for target `check-am' failed
> 
> make[1]: *** [check-am] Error 2
> 
> make[1]: Leaving directory `/cygdrive/c/build/netcdf-fortran-4.2/nf_test'
> 
> Makefile:422: recipe for target `check-recursive' failed
> 
> make: *** [check-recursive] Error 1
> 
> 
> 
> I configured with:
> 
> 
> 
> CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib
> LD_LIBRARY_PATH=/usr/local/lib ./configure
> 
> 
> 
> Also I saw the thread [netcdf # LPS-130131] and configured with the
> suggested changes, but that didn't work either.
> 
> I attach the config.log file for configuring with
> CPPFLAGS=-I/usr/local/include,-DgFortran LDFLAGS=-L/usr/local/lib
> LD_LIBRARY_PATH=/usr/local/lib ./configure

I think the problem with the above is the comma delimiter in CPPFLAGS.  On Unix
systems, you have to use a blank delimiter and quote the combination, as in:

  CPPFLAGS="-I/usr/local/include -DgFortran" LDFLAGS=-L/usr/local/lib 
LD_LIBRARY_PATH=/usr/local/lib ./configure

I assume the same is needed when using cygwin.

--Russ

Russ Rew                                         UCAR Unidata Program
address@hidden                      http://www.unidata.ucar.edu



Ticket Details
===================
Ticket ID: GDO-757215
Department: Support netCDF
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.