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

Re: compiling xgks on DEC alpha

Hi Keith!

>Date: Fri, 5 Feb 1999 17:34:31 -0800
>From: "Keith D. Sashegyi" <address@hidden>
>Organization: Naval Research Laboratory
>To: address@hidden
>Subject: compiling xgks on DEC alpha
>Keywords: 199902060134.SAA06570

In the above message, you wrote:

> Steve,
> 
>       I am trying to comipile the xgks package which I downloaded from your
> web site.  I have a graphics package that uses NCAR graphics and the xgks
> package, which I am setting up on a DEC Alpha running Digital Unix OSF3.2c.
> The compilation fails when trying to open a file like .. m4 ..
>        Do you know of anyone who has compiled the xgks package on the DEC
> alpha workstation?

Me.

> Any suggestions?
> 
> Thanks,
> Keith Sashegyi
> 
> P.S.  I don't know if you remember me from RSMAS, but I was in an
> Introductory Oceanography Lab that you conducted for the beginning grad
> students in 75 or 76.

Yeah.  I remember you!  So you're at ONR now.  Cool!

> ----------------------------------------------------------------------------
> Code 7531
> Marine Meteorology Division
> Naval Research Laboratory
> 7 Grace Hopper Ave, MS# 2
> Monterey, CA  93943-5502
> 
> Tel# (408) 656-4464
> Fax# (408) 656-4769
> email: address@hidden
> ----------------------------------------------------------------------------
> 
> -----------------------------------------------------------------------------
> The output of the make script running in Bourne shell follows:
> $ make CFLAGS=-O2 LDFLAGS=-s
> 
> making `all' in directory /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/port
> 
> 
> making `all' in directory
> /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/port/fortc
> 
> 
> returning to directory /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/port
> 
> ar rcuv libudport.a uddummy.o
> ranlib libudport.a
> 
> returning to directory /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5
> 
> 
> making `install' in directory
> /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/port
> 
> make  /afs/nrlmry/users/sashegyi/xgks/lib
> LIBDIR=/afs/nrlmry/users/sashegyi/xgks/lib
> `/afs/nrlmry/users/sashegyi/xgks/lib' is up to date.
> ar rcuv /afs/nrlmry/users/sashegyi/xgks/lib/libudport.a uddummy.o
> ranlib /afs/nrlmry/users/sashegyi/xgks/lib/libudport.a
> 
> returning to directory /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5
> 
> 
> making `all' in directory /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/src
> 
> 
> making `all' in directory
> /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/src/fortran
> 
> /afs/nrlmry.navy.mil/users/sashegyi/xgks-2.5.5/port/fortc/fortc -O osf
> control.fc > control.c  || (rm -f control.c; exit 1)
> 
> m4:-:1 can't open file
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.
> *** Exit 1
> Stop.
> $

Hmm...  Do you have the file "port/fortc/osf.m4"?  If not, then put the
enclosed file there and retry.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>

--------Begin port/fortc/osf.m4
divert(-1)
define(`M4__SYSTEM', OSF)
define(`M4__FORTRAN_DEFINES',
`
#define FORTRAN_HAS_NO_BYTE
')
# transformation from fortran name to name of C module
define(`NAMEF',`$1_')   # for Sun and most unixes, just append an underscore
# transformation from string name to corresponding argument name
define(`STRINGF',`$1')
# extra arguments, if any, for argument lengths
define(`STRINGX',`, $1_len')  # one extra stringlen parameter
define(`REALX',`')
define(`INTEGERX',`')
define(`FUNCTIONX',`')
define(`DOUBLEX',`')
# declaration to be used for argument name descriptor
define(`STRINGD',`
    char      *$1;
    int        $1`'`_len';') # declare argument string with extra stringlen 
parameter
# declarations and initializations of canonical local variables
define(`STRINGL',`')
# FORTRAN declaration for a long integer (e.g. integer*4 for Microsoft)
define(`LONG_INT',`integer')
# FORTRAN declaration for a short integer (e.g. integer*2)
define(`SHORT_INT',`integer*2')
# FORTRAN declaration for an integer byte (e.g. integer*1 or byte)
define(`BYTE_INT',`integer')
# FORTRAN declaration for double precision (e.g. real for a Cray)
define(`DOUBLE_PRECISION',`double precision')
# FORTRAN syntax for including a file
define(`M4__RIGHT_QUOTE',')
define(`F_INCLUDE',`      `include' M4__RIGHT_QUOTE`'$1`'M4__RIGHT_QUOTE')
divert(0)dnl