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

Re: Problems building netcdf-2.4.3 on CRAY T90

> > > > Are you having trouble building netcdf-2.4.3 the "first time",
> > > > or is this from the second pass, building with the netcdf-3 lib?
> > >
> > > First time !
> > >
> > > I will go ahead and do the preliminaries for 3.2a, however, and see
> > > what happens - maybe there'll be a clue...
> > >
> > is different? Are you sharing the source directory over NFS with the SGI
> > and neglecting to do a 'make distclean'? Retaining a 'config.cache' file
> > between builds on different architectures can really hose things up.
>
> I just verified that 2.4.2 builds and tests OK on the T90.
>
> No, I do not share any source directories - I copy the tar file over,
> untar it, and build from the ground up.
>
> Note that I do *not* have any of Swanson's "*CRAY*" switched turned on,
> which may (or may not) make the 2.4.2 vs. 2.4.3 mystery clearer.
>
> One of our local Crayons took a look at this and traced it down to a
> failure making the call ffopens(flexible file open) in xdrffio.c.
> (Obviously, this is where the "Unable to open file" message is coming
> from.)  He said it appeared that the permissions on the file got
> garbled somewhere along the way (though I do not know where), as though
> something got overwritten.
>
> I did notice that some "absurd argument" checks were removed from
> "nctest/emalloc.c", if that means anything.
>
> Any clues here?

John:

>From our point of view, the failure to of netcdf-2.4.3 to build/work on the T90
is a bigger problem than your original problem, so, I'm opening an new case for
this problem.

Steve and I looked over the source changes between netcdf-2.4.2 and
netcdf-2.4.3. We don't see anything obvious to account for the problem you
are seeing. The prime suspects are 'configure' and changes to xdrffio.c.

Let's concentrate on netcdf-2.4.3/libsrc.
Please send me the output of trying 'make test' in that directory.
We would want to see what flags are being set when objects are compiled,
so be sure that at least one .o file gets rebuilt. (rm xdrffio.o, for example.)
We would also like to compare the compiler options and -D flags that end up
being used in your netcdf-2.4.2 build with what happens here.

-glenn