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.
Robert, Under Linux, sometimes the ranlib does not get run by make. This does not always happen..... All you need to do for the error message below is: ranlib $GEMLIB/device.a You probably want to make sure that a non-execuatble garp was left in the $GARPHOME/linux directory (remove it it it is there), then Then resume the build with "make all" Steve Chiswell On Fri, 26 Apr 2002, Robert Mullenax wrote: > We have a new Beowulf cluster running Red Hat Linux 7.2 based on the (I > believe) 2.4.9 kernel. > GCC version is 2.96. > > While trying to compile GEMPAK5.6f I get a bunch of these "could not read > symbols"errors which > result in nothing but the decoders (dc programs) actually being built. > > Does anyone have any ideas here? I am relatively new to Linux. Here is an > example below. > > g77 -fno-second-underscore -I/WX/users/nawips/GEMPAK/gempak/include > -I/WX/users/nawips/GEMPAK/gempak/include/Linux -c > -I/WX/users/nawips/GEMPAK/comet/garp/gempak/linux ../imisub.f > make[3]: Leaving directory `/WX/users/nawips/GEMPAK/comet/garp/gempak/linux' > /WX/users/nawips/GEMPAK/lib/linux/device.a: could not read symbols: Archive > has no index; run ranlib to add one > collect2: ld returned 1 exit status > make[2]: *** [linux/garp] Error 1 > > > Thanks, > Robert Mullenax > > > Weather Systems Administrator > Universal Weather and Aviation >