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

20021114: building LDM 5.2.2 at NIU (cont.)

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: 20021114: building LDM 5.2.2 at NIU (cont.)
  • Date: Thu, 14 Nov 2002 09:25:23 -0700
>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200210050242.g952g0127088 McIDAS-XCD DMRAOB DMSYN

Gilbert,

>BTW, for ldm 5.2.2., I had to take out the "c89" references in the 
>source directory "configure" file to get it to compile.

The easiest way to do this is to define environment variables before
running configure.  The set of environment variables I use on Linux
systems for both LDM and McIDAS builds is:

CC=/usr/bin/gcc
CPPFLAGS=-DNDEBUG -Df2cFortran
CFLAGS=-O
FC=/usr/bin/g77
FFLAGS=-O -Wuninitialized -fno-automatic
CXX=

Since these settings will be used each time you build, it is easiest
to put their definitions in your shell-specific definition file.  Since
you are using the C shell for 'ldm' (as recommended), the entries would
be:

setenv CC /usr/bin/gcc
setenv CPPFLAG "-DNDEBUG -Df2cFortran"
setenv CFLAGS -O
setenv FC /usr/bin/g77
setenv FFLAGS "-O -Wuninitialized -fno-automati"
setenv CXX

Remember, after changing environment variables, you need to do a
'make distclean' (if the previous configure step had gotten to the point
of creating Makefiles) and then rerun configure.

Tom