Re: ncargf90 woes

From: Kate Hedstrom (kate@XXXXXX)
Date: Thu Feb 15 2001 - 08:37:18 MST

  • Next message: Paul Markowski: "RE: ncargf90"

    > .. when I do this on my machine (and I've tried Suns too, so the
    > problem doesn't appear to be unique to linux), I get all sorts of symbol
    > referencing errors (see below):
    >
    > ncargf90 -o stuff stuff.f
    > f90 -O -o stuff stuff.f -L/opt/ncargraph/lib -L/usr/openwin/lib
    > -L/usr/dt/lib -lncarg -lncarg_gks -lncarg_c -lX11 -lXext
    > Undefined first referenced
    > symbol in file
    > __e_wsle /opt/ncargraph/lib/libncarg_gks.a(g01seg.o)
    > __s_stop /opt/ncargraph/lib/libncarg.a(seter.o)
    > .
    > . (much deleted)
    > .
    > __s_wsfe /opt/ncargraph/lib/libncarg_gks.a(gerlog.o)
    > ld: fatal: Symbol referencing errors. No output written to it.
    >
    > Has anyone else ever seen this before or run f90 successfully with ncar
    > graphics? What libraries might I also need to include, and why do I not
    > need these when using ncargf77? Could it be a compiler or operating
    > system issue (although SunOS and RH Linux both gave me this problem)?

    All Fortran compilers have their own private library which they link to
    containing I/O routines, etc. You need to link to that private
    library which was used when NCARG was built. On the Sun, this
    will be under /opt/SUNWspro/lib. In Linux, this might be something like
    /usr/local/lib/libg2c.a.

    You can go to the directory in question and do something like:

    % foreach foo (lib*)
    > nm $foo | grep __s_wsfe
    > echo $foo done
    > end

    to track down which library contains the symbols.

    The other option is to rebuild NCARG with the f90 compiler
    which will do its I/O with its own private library.

    Kate

    -- 
    Kate Hedström               Institute of Marine and Coastal Sciences
    kate@imcs.rutgers.edu       Rutgers University
    



    This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 10:22:51 MST