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

Re: 19990824: building netCDF 3.4 under IRIX: missing "ar"

Deepsea,

> From: Deepsea Dawn <address@hidden>
> Subject: trouble with netCDF 3.4
> Organization: Oregon State University
> Keywords: 199908240554.XAA10634 netCDF 3.4 configure

In the above message, you wrote:

> Hi there - tried to follow install directions to the tee but still ran
> into problems (below). It may be an fecc problem? Thanks for any help!

What's "fecc"?

> Dawn Wright | Associate Professor | Department of Geosciences
> Oregon State University | Corvallis, OR 97331-5506
> http://dusk.geo.orst.edu | 541-737-1229 phone | 541-737-1200 fax
...

>     A.  The standard output of the command "uname -a".
> IRIX dusk 6.5 01221553 IP32
> 
> 
>     B.  The contents of the file VERSION, which is in the top-level
>         source directory.
> 3.4
> 
>     C.  The absolute pathnames of all compilers (C, Fortran, C++) used
>         in the build process (use the type(1) or which(1) utility to
>         determine this).
> /usr/bin/cc
> 
> 
>     D.  The file "configure.log" from step 6 above.
> creating cache ./config.cache
> checking for m4... m4
> checking user-defined C compiler "/bin/cc"
> checking C compiler... works
> checking how to make dependencies... cc -M
> checking for /bin/CC... /bin/CC
> checking C++ compiler "/bin/CC"... works
> checking how to run the C preprocessor... /bin/cc -E
> checking user-defined Fortran compiler "/bin/f77"... checking for Fortran .F 
> compiler... 
> checking for Fortran preprocessor... /bin/cc -E
> checking for math library
> checking for -lc... no
> checking for -lm... yes
> checking for ar... :
> checking for ranlib... :

On our IRIX 6.5 system, the last 2 lines above were the following:

    checking for ar... ar
    checking for ranlib... :

It appears, therefore, that the configure script was unable to locate
the ar(1) utility on your system.  This would mean that the netCDF
library wouldn't be built (as seen below).

> checking for stdlib.h... yes
> checking for sys/types.h... yes
> checking for strerror... yes
> checking whether cross-compiling... no
> checking for working ftruncate()... yes
> checking for working alloca.h... yes
> checking for alloca... yes
> checking for st_blksize in struct stat... yes
> checking for IEEE floating point format... yes
> checking for ANSI C header files... yes
> checking for size_t... yes
> checking for off_t... yes
> checking for ssize_t... yes
> checking for ptrdiff_t... yes
> checking for uchar... no
> checking whether char is unsigned... yes
> checking whether byte ordering is bigendian... yes
> checking size of short... 2
> checking size of int... 4
> checking size of long... 4
> checking size of float... 4
> checking size of double... 8
> checking size of off_t... 8
> checking size of size_t... 4
> checking for manual-page index command... 
> checking binary distribution directory... /home/ftp/pub/binary/dummy_system
> updating cache ./config.cache
> creating ./config.status
> creating macros.make
> udcreating fortran/nfconfig.inc
> creating libsrc/ncconfig.h
> 
> 
>     E.  The file "config.log", which is created in the top-level source
>         directory by the configure script during step 6 above.
...

>     F.  The file "make.log" from step 7 above.
> 
> Making `all' in directory /usr/local/netcdf/netcdf-3.4/src/libsrc
> 
>         /bin/cc -c -O -I.  -DNDEBUG attr.c
>         /bin/cc -c -O -I.  -DNDEBUG dim.c
>         /bin/cc -c -O -I.  -DNDEBUG error.c
>         /bin/cc -c -O -I.  -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c
>         /bin/cc -c -O -I.  -DNDEBUG nc.c
>         /bin/cc -c -O -I.  -DNDEBUG ncio.c
>         /bin/cc -c -O -I.  -DNDEBUG ncx.c
>         /bin/cc -c -O -I.  -DNDEBUG putget.c
>         /bin/cc -c -O -I.  -DNDEBUG string.c
>         /bin/cc -c -O -I.  -DNDEBUG v1hpg.c
>         /bin/cc -c -O -I.  -DNDEBUG v2i.c
>         /bin/cc -c -O -I.  -DNDEBUG var.c
>         : cru    libnetcdf.a attr.o  dim.o  error.o  libvers.o  nc.o  ncio.o  
> ncx.o  putget.o  string.o  v1hpg.o  v2i.o  var.o

The last line above should have been "ar cru libnetcdf.a ...".  The fact
that it wasn't is consistent with the configure script not finding the
ar(1) utility.

The configure script locates the ar(1) utility by first seeing if the
environment variable AR is set (is it?)  If not, then it looks through
your PATH.  I suggest the following:

    1.  If the environment variable AR is set, then unset it, e.g.

            $ unset AR          # Standard UNIX shell

        or

            % unsetenv AR       # csh shell

    2.  Do a "which ar" or "type ar" to locate the ar(1) utility.
        Modify your PATH environment variable as necessary to find it.

    3.  Go to the top-level source directory of the netCDF package.

    4.  Perform steps 2 through 9 near the end of the INSTALL file.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>

>From address@hidden  Wed Aug 25 17:02:40 1999

Hi again Steve,

I tried installed netCDF on my colleague's machine, which has "ar" and
the compilers installed properly and everything worked like a charm!

Sorry to trouble you and thanks for your patience!

Dawn

-- 
Dawn Wright | Associate Professor | Department of Geosciences
Oregon State University | Corvallis, OR 97331-5506
http://dusk.geo.orst.edu | 541-737-1229 phone | 541-737-1200 fax