ADL 2.0 Installation on GRAVITE - Comments

[david.tagatac]

1. In the I1.5_ADL_2.0_InstallationInstructions.pdf, after gtar'ing the Main, Input, and Output archives, the command for verifying the md5sums should be

   Code: Select all

   md5sum -c ADL_md5sum.txt | egrep -v ": OK"

2. Be sure to install the exact specified versions of the prerequisite software. In particular, the latest version of Xerces will not work; you must install version 2.8.0.
3. We needed sys admin support (root access) in order to install the Perl XML::Simple module using the CPAN prompt.
4. The following environment variables must be set in envSetup.csh:

   Code: Select all

   setenv LD_LIBRARY_PATH ${ADL_HOME}/lib:${COTS_XER_CPP_HOME}/lib:${LD_LIBRARY_PATH}
   setenv ENDIAN "LITTLE"
   setenv PATH ${PATH}:${ANT_HOME}/bin:${JAVA_HOME}/bin

[krboswell]

David,

It is also possible to install perl modules to non-standard directories. However, you will have to edit $ADL_HOME/perl/src/generateSourceFiles.pl to make it work. For instance, if you install XML::Simple to $HOME/lib/perl, you will have to insert the following line within the BEGIN{ } block in generateSourceFiles: eval 'use lib "$ENV{HOME}/lib/perl";';

In other words, change:

Code: Select all

BEGIN {
    if (defined($ENV{ADL_HOME}) && $ENV{ADL_HOME} ne "")
    {
        eval 'use lib "$ENV{ADL_HOME}/perl/modules";';
    }
    else
    {
        eval 'use lib "$ENV{PRO_HOME}/lib";';
    }
};

to

Code: Select all

BEGIN {
    if (defined($ENV{ADL_HOME}) && $ENV{ADL_HOME} ne "")
    {
        eval 'use lib "$ENV{ADL_HOME}/perl/modules";';
    }
    else
    {
        eval 'use lib "$ENV{PRO_HOME}/lib";';
    }
    eval 'use lib "$ENV{HOME}/lib/perl";';
};

[krboswell]

The following should also work, although I haven't tried it:

Code: Select all

export PERL5LIB=$HOME/lib/perl

This would obviously be better, since you wouldn't have to always modify the script file.

[rayg]

The PERL5LIB trick is what I used, though I still had to use a yum archive to get XML::Simple installed.

My early-2010 notes from installing ADL 1.0 put the perl modules in my ~/opt/cpan directory, using instructions gleaned off http://wiki.dreamhost.com/CPAN . Other notes from my notebook included reviewing ~/.cpan/CPAN/MyConfig.pm after going through the configuration, and making sure "makepl_arg" is set to q[PREFIX=/home/rayg/opt/cpan]. Then I was able to use the cpan commandline to do installs.

Also, Perl588 didn't need Getopt::Std, File::Basename, FileHandle, or Data::Dumper.

Disclaimer - I am not a perl guru.

[tdorman]

I've done a build of ADL 2.0 on GRAVITE. (proc8)
It seems to have built OK. And I think runs OK through the runDemo script.
But I seeing some warning messages from the build.
Can anyone say if this is normal. Can anyone currently compile their
installation with out having any warnings occur.

[krboswell]

Tim,

The compiler warnings from GCC are normal. We turned on more compiler warnings for GCC, apparently, than we did for the xlC compiler. Therefore, many of these warnings were new to us when we did the port to GCC/Linux. Due to tight time constraints, we considered them a low priority as they do not affect results.