[GEMPAK #WWZ-991406]: GEMPAK 5.9.3

Michael,

I was referring to the Makefile which I provided in the example, that sources
$CONFIGDIR/Makeinc.common to define GEMLIB=$NAWIPS/os/$NA_OS/lib/gemlib.a etc.

You can of course use the actual file names of gemlib.a, cgemlib.a, gplt.a. 
etc.....

Steve Chiswell
Unidata User Support



> Interesting....I'll try and digest this all though I am moving into
> increasing unfamiliar territory. I can echo $GEMPLT and get a response...but
> an echo of $GPLT yields nothing. DO I need to add the library paths to my
> .bashrc file before continuing?
> 
> 
> --

> ----- Original Message -----
> From: "Unidata GEMPAK Support" <address@hidden>
> To: <address@hidden>
> Cc: <address@hidden>
> Sent: Wednesday, November 22, 2006 2:29 PM
> Subject: [GEMPAK #WWZ-991406]: GEMPAK 5.9.3
> 
> 
> > Michael,
> >
> > For one pass linkers, you have to list the libraries in order and possibly
> > multiple
> > times due to dependencies in files getting resolved. See the Makefile in
> > the
> > sample I posted which links the libraries in order:
> > LIBINC = \
> >        $(GPLT_NC) \
> >        $(GEMLIB) \
> >        $(GPLT) \
> >        $(DEVICE) \
> >        $(GN) \
> >        $(CGEMLIB) \
> >        $(GEMLIB)
> >
> > Note that GEMLIB is listed twice since GEMLIB has routines which call GPLT
> > and CGEMLIB
> > routines which themselves require GEMLIB.
> >
> > Steve Chiswell
> > Unidata User Support
> >
> >
> >> Steve
> >>
> >> Thanks...I missed one. However, the errors I am getting are compile
> >> errors...
> >>
> >> /tmp/cco.NveXTV(.text+0x71): In function `gemwrt_':
> >> : undefined reference to `in_bdta__'
> >> /tmp/cco.NveXTV(.text+0x80): In function `gemwrt_':
> >> : undefined reference to `dg_intl__'
> >> /tmp/cco.NveXTV(.text+0x1a5): In function `gemwrt_':
> >> : undefined reference to `dg_inxt__'
> >> /tmp/cco.NveXTV(.text+0x205): In function `gemwrt_':
> >> : undefined reference to `dg_nwdt__'
> >> /tmp/cco.NveXTV(.text+0x31c): In function `gemwrt_':
> >> : undefined reference to `gd_clos__'
> >>
> >> I have linked the /home/unidata/GEMPAK5.9.3/os/linux/lib/gemlib.a into
> >> the
> >> compile as well....
> >> --
> >> Dr. Michael  Dickinson
> >> Senior Research Scientist
> >> Accurate Environmental Forecasting, Inc.
> >> 165 Dean Knauss Dr.
> >> Narragansett, RI 02882
> >> 401.788.9031 (voice)
> >> 401.788.9034 (fax)
> >> http://www.accufore.com
> >>
> >> ----- Original Message -----
> >> From: "Unidata GEMPAK Support" <address@hidden>
> >> To: <address@hidden>
> >> Cc: <address@hidden>
> >> Sent: Wednesday, November 22, 2006 1:14 PM
> >> Subject: [GEMPAK #WWZ-991406]: GEMPAK 5.9.3
> >>
> >>
> >> >> Steve
> >> >>
> >> >> Thank you for your response. I have only now started looking at the
> >> >> examples. Essentially I have two routines, one that reads from an
> >> >> existing
> >> >> GEMPAK grid file and one that writes to one.
> >> >>
> >> >> So I am looking to modify calls like
> >> >>
> >> >> in_bdta, gd_opnf, gd_rdat, and gd_wpgd
> >> >
> >> > Keep in_bdta.
> >> >
> >> > All programs which use the grid diagnostics MUST call DG_INTL as shown
> >> > in
> >> > the examples.
> >> >
> >> > Steve Chiswell
> >> > Unidata User Support
> >> >
> >> >
> >> >>
> >> >> In my writing routine, I incorporated DG_NWDT, DG_INXT but was unable
> >> >> to
> >> >> get
> >> >> past the compile stage...
> >> >>
> >> >> Thanks
> >> >> --
> >> >> Dr. Michael  Dickinson
> >> >> Senior Research Scientist
> >> >> Accurate Environmental Forecasting, Inc.
> >> >> 165 Dean Knauss Dr.
> >> >> Narragansett, RI 02882
> >> >> 401.788.9031 (voice)
> >> >> 401.788.9034 (fax)
> >> >> http://www.accufore.com
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Unidata GEMPAK Support"
> >> >> <address@hidden>
> >> >> To: <address@hidden>
> >> >> Cc: <address@hidden>
> >> >> Sent: Wednesday, November 08, 2006 4:38 PM
> >> >> Subject: [GEMPAK #WWZ-991406]: GEMPAK 5.9.3
> >> >>
> >> >>
> >> >> > Michael,
> >> >> >
> >> >> > I put together an example of a routine that handles writing of a
> >> >> > grid
> >> >> > (eg
> >> >> > for
> >> >> > porting from gd_wpgd) that you might find useful. See:
> >> >> > http://www.unidata.ucar.edu/software/gempak/GEMPAK5.9/newgrid_example.tar.gz
> >> >> >
> >> >> > This routine creates a new grid file through GD_CREF which you do
> >> >> > not
> >> >> > need
> >> >> > if you
> >> >> > are using an existing grid file with GD_OPNF.
> >> >> >
> >> >> > Steve Chiswell
> >> >> > Unidata User Support
> >> >> >
> >> >> >
> >> >> >
> >> >> >> I have read through the GEMPAK 5.9.3 migration document
> >> >> >> (http://www.unidata.ucar.edu/software/gempak/GEMPAK5.9/GEMPAK_Grid_library_upgrade.html)
> >> >> >> but it is still not clear to me how to make the changes I need. I
> >> >> >> have
> >> >> >> a
> >> >> >> number of Fortran routines that read from GEMPAK data files using
> >> >> >> in_bdta, gd_opnf, gd_wpgd that I (clearly) need to replace but it
> >> >> >> is
> >> >> >> not
> >> >> >> clear to me how best to fulfill that goal.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Dr. Michael  Dickinson
> >> >> >> Senior Research Scientist
> >> >> >> Accurate Environmental Forecasting, Inc.
> >> >> >> 165 Dean Knauss Dr.
> >> >> >> Narragansett, RI 02882
> >> >> >> 401.788.9031 (voice)
> >> >> >> 401.788.9034 (fax)
> >> >> >> http://www.accufore.com
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >> > Ticket Details
> >> >> > ===================
> >> >> > Ticket ID: WWZ-991406
> >> >> > Department: Support GEMPAK
> >> >> > Priority: High
> >> >> > Status: Closed
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >> > Ticket Details
> >> > ===================
> >> > Ticket ID: WWZ-991406
> >> > Department: Support GEMPAK
> >> > Priority: High
> >> > Status: Closed
> >> >
> >>
> >>
> >>
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: WWZ-991406
> > Department: Support GEMPAK
> > Priority: High
> > Status: Closed
> >
> 
> 
> 


Ticket Details
===================
Ticket ID: WWZ-991406
Department: Support GEMPAK
Priority: High
Status: Closed