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

[netCDF #GLW-819576]: Further NetCDF linkage problems with Portland Fortran

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: [netCDF #GLW-819576]: Further NetCDF linkage problems with Portland Fortran
  • Date: Tue, 22 Mar 2016 10:36:08 -0600
Hello Mathew,

Thank you for letting us know; sorry for the delayed response, I have been out 
of the office for the past week.  I will take a look at this and make the 
appropriate changes, thanks!

Have a great day,

-Ward

> I recently contacted you regarding a problem linking the NetCDF
> unit tests with Portland Fortran. This was using v15.1 of the
> Portland compiler. The issue is detailed in your bug tracker as
> #PEG-669046. The problem was fixed in a subsequent release.
> 
> Today I have been compiling NetCDF v4.3.3.1 using Portland v15.7
> and I notice the same problem has re-appeared but against a
> different test. In my original report the issue was with
> am_f03tst_vars2. This has been fixed. Now the problem is seen
> with tst03_f77_v2_OBJECTS. Again it is missing
> "module_tests.$(OBJEXT)" in nf03_test/Makefile.in.
> 
> As you pointed out previously your fix would need to be in
> Makefile.am.
> 
> I hope this information is useful to you.
> 
> --
> Matthew Hambley
> Scientific Software Engineer
> Met Office Hadley Centre, Exeter, UK
> 
> 


Ticket Details
===================
Ticket ID: GLW-819576
Department: Support netCDF
Priority: High
Status: Closed