next up previous contents
Next: CUTE log Up: Installation and usage Previous: Checking the integrity of   Contents

Attempting installation on an unsupported architecture

As far as UNIX-like platforms are concerned, it should not be too difficult to port CUTEr. This might require, however, a number of changes in several files. We suggest in this section where some of these modifications could take place. Additional modifications may be necessary, depending on your local system.

First, the installation scripts themselves may need to be altered, for compatibility reasons: the local C shell, if there is one, may be different, or require different command-line options. For example, the very first line of install_cuter may be #!/bin/csh under Solaris, but has to be #!/bin/csh -f on LINUX machines. All the scripts included in the CUTEr distribution are thoroughly self-documented and should be rather quickly understood by anyone familiar with the UNIX environment and the C shell. Similarly, as all the CUTEr scripts use the C shell, they may all need corresponding modifications.

You may need to alter a few Umake configuration files stored under $CUTER/config, such as all.cf and/or <your_system>.cf. Also make sure that new compilers that you define there appear in

$CUTER/build/arch/f.arch or $CUTER/build/arch/c.arch

for Fortran and CC++ compilers respectively, with matching symbols. More specifically, if your compiler name is abc, then the symbol which represents it in the configuration file must be ``Isabc'' and the block defining your compiler must look like

#ifdef Isabc
#define CompilerTagId           abc
#define umakeCompilerFlag       -DIsabc
#define CompileCmd              abc77 -c
#define LoadCmd                 abc77
#define CompilerIsF9095         yes
#define Compile9095Cmd          abc90 -c
#define Load9095Cmd             abc90
#define FortranFlags            -O
#define NumberOfBytes           8
#endif
where abc77 and abc90 represent the true compiler command for Fortran 77 and Fortran 90/95 source files respectively; these need not match the abc pattern. If the compiler abc does not support Fortran 90/95, then CompilerIsF9095 should be set to no in the above block, and the two symbols Compile9095Cmd and Load9095Cmd should be defined to the empty string, i.e. :
#ifdef Isabc
#define CompilerTagId           abc
#define umakeCompilerFlag       -DIsabc
#define CompileCmd              abc77 -c
#define LoadCmd                 abc77
#define CompilerIsF9095         no
#define Compile9095Cmd          
#define Load9095Cmd             
#define FortranFlags            -O
#define NumberOfBytes           8
#endif

If you wish to support a compiler for your platform which is already defined in all.cf, but the compiler options are different on your platform, you need to make sure that your settings are not overwritten by those in all.cf. You might, for this, define a flag in you_platform.cf as part of the compiler definition and modify all.cf so as to skip the corresponding compiler definition. For instance, compiler n95 is defined in both mac.cf and all.cf. Since all.cf will be sourced in all cases, the compiler definition in mac.cf contains the line

#define n95Defined
In all.cf, the definition of n95 will be skipped if the symbol n95Defined has already been defined:
#ifdef Isn95
#ifndef n95Defined
...
#endif
#endif

The file $CUTER/build/scripts/makefile.cmds will need to be altered so as to include your new your_system.cf. This modification is however trivial.

If your system does not support man pages, these will be provided in pdf and other formats on the CUTEr website, as will updates to this general documentation and other information.

Fortran 77 files should be standard and compatible for the most part. Check your local compiler documentation for possible incompatibilities. If there is no available Fortran 90 compiler on your platform, you will not be able to use those tools (unless you write one).

If your new installation procedure is a success, we will be pleased to include it in the next releases of CUTEr, with proper credits. In this case, please send detailed information on your changes and on your local system. On the other hand, please feel free to contact us if you think we may be of some help.

Many thanks and again, good luck!


next up previous contents
Next: CUTE log Up: Installation and usage Previous: Checking the integrity of   Contents
Dominique Orban 2005-03-24