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

[netCDF #YVQ-214480]: Patch for Intel fortran on Mac OS

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 #YVQ-214480]: Patch for Intel fortran on Mac OS
  • Date: Tue, 13 Dec 2011 14:57:28 -0700
> Great.  Following the new sentence about autoreconf, I think it should
> say something like "Then perform a complete build in the normal way,
> starting with running the configure script".

Yes, that's more helpful.  For the new split netcdf-fortran-4.2 release, 
I actually need to apply the patch to the m4/libtools.m4 in the fortran 
release sources in addition to (or maybe instead of) in the C release.

I'm currently having problems in the Fortran library linking step, but it
has nothing to do with the patch to libtool.m4.  libtool is called with a
link argument "-wl,-force_load" and gives the error message:

  /usr/bin/libtool: unknown option character `f' in: -force_load

I need to do a little Googling research on this, but in the meantime, I may
be able to test the modified configure for 4.1.3 and 4.1.2 in parallel
and make that available ...

--Russ

> On Tue, Dec 13, 2011 at 1:33 PM, Unidata netCDF Support
> <address@hidden> wrote:
> > Dave,
> >
> >> On the known problems page, it would be good to augment this sentence
> >> as follows:  "Equivalent fixes may also work with Netcdf versions as
> >> far back as 3.6.2, which are all based on libtool".
> >
> > Done.
> >
> >> Yes, patched and tested configure scripts for various Netcdf versions
> >> will be more user friendly than the raw libtool patch.  The patch
> >> requires extra user steps and a compatible set of GNU build utilities.
> >>
> >> Consider removing the last paragraph where I discuss running configure
> >> twice, and replace it with a better recipe using autoreconf.  I think
> >> you have a better understanding of how to run the GNU build system.
> >
> > Done.
> >
> >> Can you include "NOAA/PSD/CIRES" after my name on the known problems
> >> page?   They supported my R&D on this.  Thank you.
> >
> > Done.
> >
> > I'm currently testing with the new configure script on the snapshot release,
> > and will test on 4.1.3, 4.1.2, and 4.1.1 shortly.
> >
> > --Russ
> 
> 

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



Ticket Details
===================
Ticket ID: YVQ-214480
Department: Support netCDF
Priority: Normal
Status: Closed