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

[netCDF #XFP-419275]: configure/build problem

> With netCDF 3.6.2 it looks like the value of FCFLAGS is not being
> used when compiling the fortran source in nf_test; it appears (by
> experimentation) to use the value of FFLAGS; I don't think this
> is right.  Here's a snippet from a configure/build/test session:
> 
> % ./configure --with-pic \
> FC=f95 FCFLAGS="-O -PIC -w -mismatch -ieee=full" \
> CC=gcc CXX="" CFLAGS=-O CPPFLAGS="-DNDEBUG -DNAGf90Fortran"
> ...
> checking if we need to add to FFLAGS for ifort compiler... FFLAGS=-g
> (I have no ifort compiler in my path -- what's it doing here?)
> 
> % make
> ...
> /bin/sh ../libtool --mode=compile f95 -I../libsrc -I.  -O -PIC -w -mismatch 
> -ieee=full -c -o typeSizes.lo typeSizes.f90
> libtool: compile:  f95 -I../libsrc -I. -O -PIC -w -mismatch -ieee=full -c 
> typeSizes.f90  -o typeSizes.o
> (This is as expected; the value of my FCFLAGS is used.)
> 
> % make test
> ...
> f95 -DHAVE_CONFIG_H -I. -I. -I.. -I../fortran   -DNDEBUG -DNAGf90Fortran   
> -I../libsrc -I../f90 -g -c -o nf_test.o nf_test.F
> (It's using FFLAGS instead of my FCFLAGS.  Compilation of this test fails
> without the "-mismatch" compiler option!)
> 
> Cheers,
> Neil
> 
> --
> Neil Carlson                                  email:  address@hidden
> Los Alamos National Laboratory                office: 505.665.6386
> CCS-2, Computational Physics and Methods      fax:    505.665.4972
> P.O. Box 1663, MS D413
> Los Alamos, NM 87545
> 
> 

Howdy Neil!

Thanks for pointing this out. I will look into this and email you when I get a 
fix in the daily snapshot build...

Thanks!

Ed

Ticket Details
===================
Ticket ID: XFP-419275
Department: Support netCDF
Priority: Emergency
Status: Open