declare -x G4HERE="/usr/local"
declare -x G4INSTALL="/usr/local/geant4.6.2.p01"
declare -x G4LISTS_BASE="/usr/local/geant4.6.2.p01/hadronic_lists"
declare -x G4SYSTEM="Linux-g++"

and

declare -x LD_LIBRARY_PATH="/usr/local/CLHEP/lib:/usr/local/geant4.6.2.p01/hadronic_lists:/usr/local/Inventor/lib:"
declare -x OLDPWD="/usr/local/geant4.6.2.p01/hadronic_lists"

if(cascadeParticle != NULL) delete cascadeParticle;
if(aFragment != NULL) delete aFragment;

[root@cdms geant4.6.2.p01]# ./Configure -install
 
 
 
                --- Geant4 Toolkit Installation  ---
 
 
 
 
 
This installation shell script will examine your system and ask you questions
to determine how the Geant4 Toolkit should be installed.  If you get stuck on
a question, you may use a ! shell escape to start a subshell or execute a
command.  Many of the questions will have default answers in square brackets;
typing carriage return will set the default.

On AFS it is allowed to specify either absolute or relative
paths (i.e. starting with the ~username construct).
[Type carriage return to continue] 

The prompt used in this script allows you to use shell variables and backticks
in your answers. You may use $1, $2, etc...  to refer to the words in the
default answer, as if the default line was a set of arguments given to a
script shell. This means you may also use $* to repeat the whole default line.

Everytime there is a substitution, you will have to confirm.  If there is an
error (e.g. an unmatched backtick), the default answer will remain unchanged
and you will be prompted again.

Running 'Configure -d' will bypass nearly all the questions and
use the computed defaults (or answers saved in a configuration
previously generated).

Type 'Configure -h' for a list of options.

You may also start interactively and then answer '& -d' at any prompt to turn
on the non-interactive behaviour for the rest of the execution.

[Type carriage return to continue] 

Much effort has been spent to ensure that this shell script will run on any
Unix system. If despite that you can't run Configure for some reason, you'll
have to set the proper environment variables by hand and follow the "manual"
installation as specified in the Geant4 Installation Guide.

[Type carriage return to continue] 

Definition of G4SYSTEM variable is Linux-g++.
That stands for:

1) OS           : Linux

2) Compiler     : g++

To modify default settings, select number above (e.g. 2) 
[Press [Enter] for default settings] 
 
I can set things up so that your shell scripts and binaries are more portable,
at what may be a noticable cost in performance.  In particular, if you
ask to be portable, the following happens:

     1) Shell scripts will rely on the PATH variable rather than using
        the paths derived above.
     2) ~username interpretations will be done at run time rather than
        by Configure.

Do you expect to run these scripts and binaries on multiple machines? [n] 
 
Where is Geant4 installed?  [/root/geant4] /usr/local/geant4.6.2.p01

Do you want to copy all Geant4 headers 
in one directory? [n] 
 

(OPTIONAL) You can now customise installation directories:
  G4TMP - tmp/ containing temporary dependency (.d) and object (.o) files;
  G4LIB - lib/ containing final static (.a) or shared (.so) libraries;

1) G4TMP:               /usr/local/geant4.6.2.p01/tmp

2) G4LIB:               /usr/local/geant4.6.2.p01/lib

To modify default settings, select number above (e.g. 2) 
[Press [Enter] for default settings] 
 

Please, specify directories where the Geant4 data is installed:

1) G4LEVELGAMMADATA:            /usr/local/geant4.6.2.p01/data/PhotonEvaporation

2) G4RADIOACTIVEDATA:           /usr/local/geant4.6.2.p01/data/RadiativeDecay

3) G4LEDATA:                    /usr/local/geant4.6.2.p01/data/G4EMLOW2.3

4) NeutronHPCrossSections:      /usr/local/geant4.6.2.p01/data/G4NDL3.7

5) G4ELASTICDATA:               /usr/local/geant4.6.2.p01/data/Elastic

To modify default settings, select number above (e.g. 2) 
[Press [Enter] for default settings] 

Could not find CLHEP installed on this system!
Please, specify where CLHEP is installed (set by default):

CLHEP_BASE_DIR:                 /usr/local

According to it will be set:

CLHEP_INCLUDE_DIR
CLHEP_LIB_DIR
CLHEP_LIB

You will be asked about customizing these next. 
[/usr/local] /usr/local/CLHEP

You can customize paths of you CLHEP installation:

1) CLHEP_INCLUDE_DIR:           /usr/local/CLHEP/include
2) CLHEP_LIB_DIR:               /usr/local/CLHEP/lib
3) CLHEP_LIB:                   CLHEP

To modify default settings, select number above (e.g. 2) 
[Press [Enter] for default settings] 
 
 
 
 


By default 'static' (.a) libraries are built.

Do you want to build 'shared' (.so) libraries?
[n] y


You selected to build 'shared' (.so) libraries. 
Do you want to build 'static' (.a) libraries too?
[n] y
 
 
 


Do you want to build 'global' compound libraries? [n] 
 


Do you want to compile libraries in DEBUG mode (-g)? [n] 
 

 


  G4UI_NONE

If this variable is set, no UI sessions nor any UI libraries are built. 
This can be useful when running a pure batch job or in a user framework 
having its own UI system.
Do you want to set this variable ?
[n] 

  G4UI_BUILD_XAW_SESSION
  G4UI_USE_XAW

  Specifies to include and use the XAW interfaces in the
  application to be built.
  The XAW (X11 Athena Widget set) extensions are required to activate 
  and build this driver.
[n] y

  G4UI_BUILD_XM_SESSION
  G4UI_USE_XM

  Specifies to include and use the XM Motif based user interfaces.
  The XM Motif extensions are required to activate and build this
  driver.
[n] y
 


  G4VIS_NONE

If this variable is set, no visualization drivers will be built or used.
Do you want to set this variable ?
[n] 

  G4VIS_BUILD_OPENGLX_DRIVER
  G4VIS_USE_OPENGLX

It is an interface to the de facto standard 3D graphics library,
OpenGL. It is well suited for real-time fast visualization
and prototyping. The X11 version of the OpenGL libraries is
required.
[n] y

  G4VIS_BUILD_OPENGLXM_DRIVER
  G4VIS_USE_OPENGLXM

It is an interface to the de facto standard 3D graphics library,
OpenGL. It is well suited for real-time fast visualization
and prototyping. The X11 version of the OpenGL libraries and 
the Motif Xm extension is required.
[n] y

  G4VIS_BUILD_DAWN_DRIVER
  G4VIS_USE_DAWN

DAWN drivers are interfaces to the Fukui Renderer DAWN. DAWN is
a vectorized 3D PostScript processor suited to prepare technical
high quality outputs for presentation and/or documentation.
[n] y

  G4VIS_BUILD_OIX_DRIVER
  G4VIS_USE_OIX

This driver is based on the "Hepvis" class library.
The OpenInventor driver and the Hepvis class library are based
on OpenInventor technology for scientific visualization.
The X11 version of OpenInventor is required.
[n] y

  G4VIS_BUILD_VRML_DRIVER
  G4VIS_USE_VRML

These driver generate VRML files, which describe 3D scenes to be 
visualized with a proper VRML viewer.
[n] y

  OGLHOME/include
  OGLHOME/lib

You have selected to use OpenGL driver.
Specify the correct path (OGLHOME) where OpenGL is installed in your system.
It was found in: 
[/usr] 
 


  G4LIB_BUILD_G3TOG4  

If this variable is set, it will be built G3TOG4 module.
Do you want to set this variable ?
[n] 
 


  G4ANALYSIS_USE

Activates the configuration setup for allowing plugins to
analysis tools based on AIDA (Astract Interfaces for Data
Analysis). In order to use AIDA features and compliant analysis
tools, the proper environment for these tools will have to be
set (see documentation for the specific analysis tools).
[n] y
 
End of configuration phase.
 
 
Creating configuration setup file...

WARNING: the generated configuration file
can be edited if necessary!
You can introduce any change to the configuration file
/usr/local/geant4.6.2.p01/.config/bin/Linux-g++/config.sh before the final installation. 
To do so, use a shell escape now (e.g. !vi /usr/local/geant4.6.2.p01/.config/bin/Linux-g++/conf
ig.sh).

Press [Enter] to start installation or use a shell escape to edit config.sh: 

####################################################
# Your Geant4 installation seems to be successful!  
# To be sure please have a look into the log file:  
# /usr/local/geant4.6.2.p01/.config/bin/Linux-g++/g4make.log                              
####################################################