970227: netcdf-3.3a "make test" error

John,

>Date: Wed, 26 Feb 1997 16:10:34 -0500 (EST) 
>From: address@hidden (John Sheldon)
>Organization: Princeton/GFDL
>To: address@hidden (Steve Emmerson)
>Subject: Re: 970226: netcdf-3.3a "make test" error 
>Keywords: 199702262036.NAA23701

In the above message, you wrote:

> > Would you please send me a recap of the problem.  Please include the
> > following:
> > 
> >     Standard output of `uname -a`
> >     Standard output of the `configure' script.
> >     Standard output of a `make'.
> 
> All tacked on the bottom of this mail...

This problem appears to be one for the netCDF-3 creator, Glenn Davis.  
I'll forward it to him.

> 
> BTW, any luck figuring out what the problem was with the tar file?  It
> appeared to be installing directories as plain files.  This ends up
> giving you stuff like:
> 
> cmd-3746 tar: x netcdf-3.3a, 0 bytes, 0 tape blocks
> cmd-1004 tar: Cannot create 'netcdf-3.3a/src'.
> cmd-3749 tar: mkdir 'netcdf-3.3a/src' failed: Not a directory
> cmd-1004 tar: Cannot create 'netcdf-3.3a/src/INSTALL'.

I've only seen this once before and it was on the same system.  I
suspect that your tar(1) is broken.

[Talking about building the netCDF package on a T3D or T3E]
> Painful??

You have to use a special I/O library that's supplied by CRI (called
`par_io' for `parallel I/O').  We don't have it.  Here's something
relevant from the netCDF support email archive:

    From: Russ Rew <address@hidden>
    To: address@hidden (Juliana Rew)
    Subject: Re: netCDF on T3D? 

    Hi,

    > Jim Rosinski in CGD asked if we had netCDF on our T3D. Had you heard
    > anything about the port (and whether it's going to be put up here)?

    Steve Luzmoor of CRI (sits, or at least used to sit, at NERSC) developed
    the first version of a "par_io" library for parallel I/O and made the
    modifications to the netCDF source to make it work on a T3D.

    The current version, 2.4.3, contains the mods for the T3D that we got
    from Steve Luzmoor.  These reference functions from the Cray par_io
    library prototype that we can't distribute with netCDF, so you may have
    to obtain the current version of that library from Cray.  While we were
    integrating these changes, it seemed that the par_io interfaces were
    changing as well and more changes were planned, so it's possible that
    the current netCDF release may need some tweaking to work with the
    current par_io release.  If there are problems building the current
    release for T3D with the par_io library that CRI can't solve, we would
    want to know about them.

    --Russ

--------
Steve Emmerson   <address@hidden>