[McIDAS #QAF-536313]: mcidas2009/g2clib/Makefile

Hi Kelly,

re:
> CC=
> this is left blank. when jasper goes to build, it interprets CFLAGS
> as the command. specifying a compiler here led to a successful build.

It appears that whoever was building McIDAS-X did not fully follow
the instructions in the Unidata McIDAS-X User's Guide that describe
how the environment for the user building McIDAS-X (typically 'mcidas')
should be defined:

Unidata HomePage
http://www.unidata.ucar.edu

  Software -> McIDAS
  http://www.unidata.ucar.edu/software/mcidas/

    Documentation
    http://www.unidata.ucar.edu/software/mcidas/#documentation

      User's Guide
      http://www.unidata.ucar.edu/software/mcidas/current/users_guide/toc.html

In Chapter 1:

Installing McIDAS-X on Unix or Mac OS X Workstations
http://www.unidata.ucar.edu/software/mcidas/current/users_guide/InstallingMcIDAS-XonUnixorMacOSXWorkstations.html

  Preparing the mcidas Account
  
http://www.unidata.ucar.edu/software/mcidas/current/users_guide/PreparingthemcidasAccount.html

The last page describes the lines to add to one's shell-specific definition file
(e.g., .cshrc for C-like shells, .bash_profile for BASH, etc.).  For instance, 
if
the 'mcidas' user's shell is BASH, then add the following to 
~mcidas/.bash_profile:

# McINST_ROOT and VENDOR conforming shell defines
# needed to bulid McIDAS
McINST_ROOT=$HOME
VENDOR=-gfortran
export McINST_ROOT VENDOR

# NOTE: uncomment the next two lines that set MySQL_ROOT if you
#       want to build with MySQL support:
#       - leave the value blank if MySQL is installed in a standard
#         location
#       - specify the value as the root directory of the MySQL
#         installation if MySQL is not installed in a standard
#         location
# MySQL_ROOT=TRUE
# export MySQL_ROOT

if [ -e $HOME/admin/mcidas_env.sh ]; then
  . $HOME/admin/mcidas_env.sh
fi

After adding these lines and assuming that the McIDAS-X distribution
file (mcidasx2009.tar.gz) has been unpacked, one would need to source
the shell file:

<as 'mcidas'>
cd ~mcidas
. .bash_profile

This causes the contents of the ~mcidas/admin/mcidas_env.sh file to
be sourced, and then all macro definitions needed (e.g., CC, etc.)
will be defined.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: QAF-536313
Department: Support McIDAS
Priority: Normal
Status: Closed