20040722: Problems with v5.7.2p2

Jon,

It sounds the build was restarted at some point without doing a 
"make clean" such that you got a "main" routine in a program .o
file added into one of the archives.

The best way to clear this up is to:
cd $NAWIPS
make distclean   <-- to remove all the libraries in $GEMLIB
make all install

if your build stops  in the middle of a build, you should
run "make clean" before restarting. This will remove
any .o files in the build tree.

Steve Chiswell
Unidata User Support




>From: "Case.Jon" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200407221655.i6MGtvaW029531

>Dear Unidata support,
>
>I just installed GEMPAK v5.7.2p2 in order to have the Level II radar
>display capabilities.  
>The previous version I had installed was version 5.6.j.
>
>Using the default compilers on our IBM/Linux Fedora Core 2 OS,
>everything seemed to compile and build just fine.  
>However, when I try to run any program, the program immediately runs and
>displays an x-window.  It seems to be looking for a parameter file for
>each program, which I can't figure out.  Also, "display", "list", and
>other such commands do not work, so I'm not able to look at the current
>settings for the parameters.  
>
>I looked through the web documentation, but could not find any
>information on GEMPAK program format changes.  Have I missed some
>details on program structure modifications, or does it sound like our
>GEMPAK install did not go properly?
>
>Thanks much for your help!
>Jonathan
>
>-----------------------------------------------------------------
>Jonathan L. Case, Meteorologist
>ENSCO Inc. / Applied Meteorology Unit
>1980 N. Atlantic Ave., Suite 230
>Cocoa Beach, FL 32931
>Voice: (321) 853-8264
>Fax:    (321) 853-8415
>---------------------------------------------------------------- 
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.