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

[netCDF #MKR-854500]: Errors - Testsuite summary for netCDF-Fortran 4.4.1



Trevor,

> I finally got the fortran-version to complete the make check process.  I
> had two problems:
> 
> 1.) I didn't have CPPFLAGS pointing to the right include directory.  Once I
> corrected that, I didn't have any reference issues with the C interface.
> 
> 2.) However, 'make check' was not completing due to F77 routine
> tst03_f77_v2.F, not able to recognize module routine "tests" in
> module_tests.F90.  My workaround was I re-compiled netcdf-C with additional
> option '--disable-v2'and then the Fortran-version 'make check' passed.
> 
> I tested my own parallel implementation and it seems to work fine.


That's goof to hear, thanks for reporting what worked.  Looking at your
original question, I now see that CPPFLAGS was not set according to the
netcdf-fortran build instructions, and I should have noticed that.

--Russ

> address@hidden> wrote:
> 
> > > Correction to my last statement:  netcdf-fortran would not complete
> > "*make
> > > check*"
> >
> > According to the instructions in step 3 under the "Building with shared
> > libraries"
> > section of
> >
> >   http://www.unidata.ucar.edu/netcdf/docs/building_netcdf_fortran.html
> >
> > you probably need to set LD_LIBRARY_PATH before running the configure
> > script
> > to specify where the C library is installed.  This may seem unnecessary if
> > you
> > alreadyset LDFLAGS with that library directory, but the dynamic linker for
> > shared
> > libraries doesn't use the LDFLAGS environment variable used by the
> > compilers.
> >
> > If that doesn't work, I'm stumped.
> >
> > --Russ
> >
> > > address@hidden> wrote:
> > >
> > > > Hi Russ,
> > > >
> > > > The libnetcdf.settings you are referring to is a printout I copied and
> > > > pasted from, if I remember right, after the configuration script had
> > > > completed - for my own notes.  That directory doesn't exist on my
> > system -
> > > > nor did I checkout or download that version.  It possible it may be a
> > typo
> > > > on my part - I've checked my notes and do see that line you are
> > referring
> > > > to.
> > > >
> > > > I did reconfigure *netcdf-C* a few times, so it seems likely I gave
> > you a
> > > > copy and paste of one of the past configurations (version 4.3.3-rc2) I
> > > > experimented with.
> > > >
> > > > I provided some screenshot attachments of nc-config --all and the
> > > > libnetcdf.settings file in the main directory in netcdf-c-4.3.3-rc2.
> > > >
> > > > However, I did find some older shared-library files in my install lib
> > > > directory - I had to get rid of those files to get parallel netcdf-C to
> > > > work with my code.  So, Netcdf-C parallel implementation is compiling
> > and
> > > > working fine with mu own implementations.
> > > >
> > > > After removing those shared-library files, I went back to remake
> > > > netcdf-fortran, and this time make won't complete.  It gives me a long
> > list
> > > > of undefined references to  'nc_put_xxxx','nc_inq_xxxx', etc.
> > > >
> > > > I hope this helps.
> > > >
> > > > Thanks,
> > > >
> > > > Trevor
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > address@hidden> wrote:
> > > >
> > > >> Trevor,
> > > >>
> > > >> > Yes I compiled HDF5 with parallel enabled, but I put in few more -
> > > >> here's
> > > >> > the arguments i provided the configuration script for HDF5:
> > > >> >
> > > >> > --enable-parallel --enable-fortran --enable-static
> > --enable-silent-rules
> > > >> >
> > > >> > I compiled HDF5 with gcc (mpicc wrapper)
> > > >> >
> > > >> >
> > > >> > In addition, I successfully compiled (and make check passed )
> > netcdf C
> > > >> > using:
> > > >> > --enable-parallel-tests --disable-shared --enable-netcdf-4
> > > >> > I compiled netcdf C with gcc (mpicc wrapper)
> > > >> >
> > > >> >
> > > >> > As far as I can tell, the parallel test passed. I re-ran make check
> > and
> > > >> I
> > > >> > got a pass for script run_par_test.sh.
> > > >> >
> > > >> > When I compile netcd-fortran, I set the following environment
> > variables
> > > >> for
> > > >> > compiling:
> > > >> >
> > > >> > CC=mpicc
> > > >> > FC=mpif90 ( this is using PGI compiler version)
> > > >>
> > > >> I noticed what looked like an inconsistency in the version of the
> > > >> netCDF-C library you are using for building netCDF-Fortran 4.4.1.
> > > >>
> > > >> You provided some details from the libnetcdf.settings file
> > > >> installed for netcdf-c-4.3.3-rc2, but it shows:
> > > >>
> > > >> > > > LDFLAGS:
> > > >> > >
> > -L/labs/climate/jiminglab2/Trevor/Tools/NetCDF/netcdf-4.3.2-rc2/lib
> > > >>
> > > >> was the netcdf-4.3.2-rc2 a typo, or where you really using using that
> > > >> older version of netCDF-C instead of  4.3.3-rc2?  If so, was that
> > > >> older netCDF-C library built using an HDF5 that had parallel I/O
> > enabled?
> > > >>
> > > >> Your symptoms seem to point to the use of a netCDF-C library that
> > wasn't
> > > >> properly built with parallel I/O enabled ...
> > > >>
> > > >> --Russ
> > > >>
> > > >> > address@hidden> wrote:
> > > >> >
> > > >> > > Hi Trevor,
> > > >> > >
> > > >> > > Did you build HDF5 with parallel I/O support by configuring it
> > with
> > > >> > > --enable-parallel,
> > > >> > > as instructed here?
> > > >> > >
> > > >> > >
> > > >> > >
> > > >>
> > http://www.unidata.ucar.edu/software/netcdf/docs/getting_and_building_netcdf.html#build_parallel
> > > >> > >
> > > >> > > If so, did you build the netCDF C library with
> > --enable-parallel-tests
> > > >> > > --disable-shared, as
> > > >> > > explained in the link above.
> > > >> > >
> > > >> > > If you did that, did you run "make check" for the netCDF-C build,
> > and
> > > >> did
> > > >> > > it pass all the parallel tests?
> > > >> > >
> > > >> > > --Russ
> > > >> > >
> > > >> > >
> > > >> > > > Hello netCDF Support,
> > > >> > > >
> > > >> > > > I was compiling netcdf-Fortran (4.4.1) for parallel IO support
> > and
> > > >> it
> > > >> > > seems
> > > >> > > > the all parallel tests failed (including a group test) and I
> > > >> attached the
> > > >> > > > test-suite.log file.
> > > >> > > >
> > > >> > > > Here is a copy and paste of my netcdf C configuration:
> > > >> > > >
> > > >> > > > # NetCDF C Configuration Summary
> > > >> > > >
> > > >> > > > ==============================
> > > >> > > >
> > > >> > > > # General
> > > >> > > >
> > > >> > > > -------
> > > >> > > >
> > > >> > > > NetCDF Version: 4.3.3-rc2
> > > >> > > >
> > > >> > > > Configured On: Tue Nov  4 12:53:34 MST 2014
> > > >> > > >
> > > >> > > > Host System: x86_64-unknown-linux-gnu
> > > >> > > >
> > > >> > > > Build Directory:
> > > >> > > > /labs/climate/jiminglab2/Trevor/Tools/netcdf/netcdf-c-4.3.3-rc2
> > > >> > > >
> > > >> > > > Install Prefix:
> > > >> > > > /labs/climate/jiminglab2/Trevor/Tools/netcdf/netcdf-c-4.3.3-rc2
> > > >> > > >
> > > >> > > > # Compiling Options
> > > >> > > >
> > > >> > > > -----------------
> > > >> > > >
> > > >> > > > C Compiler:
> > > >> > > >
> > > >> > >
> > > >>
> > /rc/tools/free/redhat_6_x86_64/datatools-wrf-pgfortran-gcc-login-slurm-production/bin/mpicc
> > > >> > > >
> > > >> > > > CFLAGS:  -g -O2
> > > >> > > >
> > > >> > > > CPPFLAGS: -DpgiFortran
> > > >> > > >
> > > >> > > > LDFLAGS:
> > > >> > >
> > -L/labs/climate/jiminglab2/Trevor/Tools/NetCDF/netcdf-4.3.2-rc2/lib
> > > >> > > >
> > > >> > > > AM_CFLAGS:
> > > >> > > >
> > > >> > > > AM_CPPFLAGS:
> > > >> > > >
> > > >> > > > AM_LDFLAGS:
> > > >> > > >
> > > >> > > > Shared Library: no
> > > >> > > >
> > > >> > > > Static Library: yes
> > > >> > > >
> > > >> > > > Extra libraries: -lhdf5_hl -lhdf5 -ldl -lm -lz -lcurl
> > > >> > > >
> > > >> > > > # Features
> > > >> > > >
> > > >> > > > --------
> > > >> > > >
> > > >> > > > NetCDF-2 API: yes
> > > >> > > >
> > > >> > > > NetCDF-4 API: yes
> > > >> > > >
> > > >> > > > HDF4 Support: no
> > > >> > > >
> > > >> > > > HDF5 Support: yes
> > > >> > > >
> > > >> > > > PNetCDF Support: no
> > > >> > > >
> > > >> > > > Parallel Support: yes
> > > >> > > >
> > > >> > > > DAP Support: yes
> > > >> > > >
> > > >> > > > Diskless Support: yes
> > > >> > > >
> > > >> > > > MMap Support: no
> > > >> > > > JNA Support: no
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > Please let me know if may provide anymore information.
> > > >> > > >
> > > >> > > > Regards,
> > > >> > > >
> > > >> > > > Trevor
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> > > Russ Rew                                         UCAR Unidata
> > Program
> > > >> > > address@hidden
> > > >> http://www.unidata.ucar.edu
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > Ticket Details
> > > >> > > ===================
> > > >> > > Ticket ID: MKR-854500
> > > >> > > Department: Support netCDF
> > > >> > > Priority: Normal
> > > >> > > Status: Closed
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >> Russ Rew                                         UCAR Unidata Program
> > > >> address@hidden
> > http://www.unidata.ucar.edu
> > > >>
> > > >>
> > > >>
> > > >> Ticket Details
> > > >> ===================
> > > >> Ticket ID: MKR-854500
> > > >> Department: Support netCDF
> > > >> Priority: Normal
> > > >> Status: Closed
> > > >>
> > > >>
> > > >
> > >
> > >
> > Russ Rew                                         UCAR Unidata Program
> > address@hidden                      http://www.unidata.ucar.edu
> >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: MKR-854500
> > Department: Support netCDF
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 

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



Ticket Details
===================
Ticket ID: MKR-854500
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.