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

950120: compiling on CRAY C90

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: 950120: compiling on CRAY C90
  • Date: Mon, 23 Jan 95 13:19:53 -0700
>From: Ming Cai <address@hidden>
>Organization: University of Maryland
>Subject: Re: 950120: compiling on CRAY C90 
>Keywords: 199501202055.AA21596

In the above message you wrote:

>I execute "make test" in the fortran/ subdirectory after I executed
>all of the commands you mentioned in your previous mail.  This time,
>it seems that I got some error msg.. 
>here is the output
>*********
>
>sn4021% make test
>        ar rcuv ../libsrc/libnetcdf.a jackets.o
>        ./fortc -L . -O unicos ftest.src > ftest.f
>        cf77 -c  ftest.f
>cf77 ftest.o -L../libsrc -lnetcdf -o ftest
> ldr-133 cf77: CAUTION
>     Unsatisfied external references have been encountered.
>
> Unsatisfied external references
> Entry name      Modules referencing entry
>
> NCACPY          TNCACPY
> NCADEL          TNCADEL
> NCAGT           TNCACPY  TNCAGT
> NCAGTC          TNCACPY  TNCAGT
> NCAINQ          TNCACPY  TNCAGT  TNCINQ
> NCANAM          TNCACPY  TNCADEL  TNCAGT  TNCINQ
> NCAPT           TNCAPT
> NCAPTC          TNCAPT
> NCAREN          TNCREDF
> NCCLOS          FTEST  TNCACPY  TNCADEL  TNCAGT  TNCINQ  TNCREDF  TNCV
>GT
>                 TNCVGT1  TNCVPT  TNCVPT1
> NCCRE           FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCDDEF          FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCDID           FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCDINQ          TNCINQ
> NCDREN          TNCREDF
> NCENDF          TNCADEL  TNCREDF
> NCINQ           TNCACPY  TNCADEL  TNCAGT  TNCINQ  TNCVGT
> NCOPN           FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCPOPT          FTEST
>NCREDF          TNCADEL  TNCREDF
> NCSFIL          FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCTLEN          FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCVDEF          FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCVG1C          TNCVGT1
> NCVGT           TNCVGT
> NCVGT1          TNCVGT1
> NCVGTC          TNCVGT
> NCVID           FTEST  TNCACPY  TNCADEL  TNCAGT  TNCAPT  TNCDDEF  TNCI
>NQ
>                 TNCREDF  TNCVDEF  TNCVGT  TNCVGT1  TNCVPT  TNCVPT1
> NCVINQ          TNCACPY  TNCADEL  TNCAGT  TNCINQ  TNCVGT
> NCVP1C          TNCVPT1
> NCVPT           TNCVPT
> NCVPT1          TNCVPT1
> NCVPTC          TNCVPT
> NCVREN          TNCREDF

Interesting.  The symbols in the left column are those that are defined
in the FORTRAN interface file `jackets.c'.  You should verify this by
executing *something* like the following command

    nm jackets.o | grep NCVREN

(details vary from platform to platform).  Output from the above command
should indicate that the symbol NCVREN is defined in jackets.o.  If this
is not the case, then let me know.

If the above symbol is defined, then the problem could be with the
netCDF library.  In this case, I suggest modifying the file 
fortran/Makefile to execute the command `ranlib ../libsrc/libnetcdf.a'
just after jackets.o is added to the library.  This should be around
line 208 in file fortran/Makefile.

When this is done, retry a `make test' in the fortran/ subdirectory.

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