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

20000224: gdrcm linking problems

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: 20000224: gdrcm linking problems
  • Date: Fri, 25 Feb 2000 09:34:43 -0700
The makefile installs the program, pdf, prm, err, hlp, and
stns files with:
        $(INSTALL) $(PROG) $(GEMEXE)
        $(INSTALL) gprcm.pdf $(GEMPAKHOME)/pdf
        $(INSTALL) gprcm.prm $(GEMPAKHOME)/parm
        $(INSTALL) gprcm.err $(GEMPAKHOME)/error
        $(INSTALL) gprcm.hlp $(GEMPAKHOME)/help
        $(INSTALL) nexrad.tbl $(GEMTBL)/stns

Since you are not using my Makefile, you have to install these yourself.

Steve Chiswell
Unidata User Support

On Fri, 25 Feb 2000, Devin Eyre wrote:

> Thanks for the help.  The compile script I was using didn't have the line in 
> it for $CC $CFLAGS.
> Everything seems to work except for phelp on any of the new parameters.
> 
> Steve Chiswell wrote:
> 
> > Devin,
> >
> > Since you are not using the Makefile environment that I provide,
> > you have to properly define the compiler flags in your build script.
> >
> > The compiling of all C programs for Solaris should include:
> > -DDUNDERSCORE -DSunOS
> >
> > The -DUNDERSCORE flag will tell the linker how fortran programs
> > access C subroutines with the _ character, which will solve the
> > problem you have below with rcm_ not being found.
> >
> > After you recompile all the C routines with the above cc options,
> > you should be able to link the program.
> >
> > Steve Chiswell
> > Unidata User SUpport
> 
> --
> address@hidden
> 
> 
>