20040830 NetCDF installation failure

Mark,

> To: <address@hidden>
> From: "Mark J. Wenzel" <address@hidden>
> Subject: NetCDF installation failure
> Organization: University of California at Berkeley
> Keywords: 200408272012.i7RKCc8E027857 netCDF install

The above message contained the following:

...
> Making `install' in directory /usr/netcdf-3.5.1/src/ncdump=0A=
> =0A=
> make[2]: Entering directory `/usr/netcdf-3.5.1/src/ncdump'=0A=
> test -d /usr/netcdf-3.5.1/bin || mkdir /usr/netcdf-3.5.1/bin=0A=
> cc -o ncdump -O  ncdump.o vardata.o dumplib.o ../libsrc/libnetcdf.a  =0A=
> Info: resolving _opterr by linking to __imp__opterr (auto-import)=0A=
> Info: resolving _optarg by linking to __imp__optarg (auto-import)=0A=
> Info: resolving _optind by linking to __imp__optind (auto-import)=0A=
> cp ncdump /usr/netcdf-3.5.1/bin/ncdump=0A=
> cp: `ncdump' and `/usr/netcdf-3.5.1/bin/ncdump' are the same file=0A=
> make[2]: *** [/usr/netcdf-3.5.1/bin/ncdump] Error 1=0A=
...

Why are the files

    /usr/netcdf-3.5.1/src/ncdump/ncdump

and

    /usr/netcdf-3.5.1/bin/ncdump

the same file on your system?  You can verify this by executing the
following command:

    ls -li /usr/netcdf-3.5.1/src/ncdump/ncdump /usr/netcdf-3.5.1/bin/ncdump

The build and installation procedures don't cause this situation.  Do
you have an errant symbolic link somewhere that causes the "bin" and
"/src/ncdump" directories to be the same?

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publically 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.