Hi,

I have the following easyconfig for Turbomole:

######################################################################

easyblock = 'PackedBinary'
name = 'TURBOMOLE'
version = '7.3'

homepage = 'http://turbomole.com/'
description = """TURBOMOLE is a program package for ab initio
electronic structure calculations."""

toolchain = {'name': 'dummy', 'version': ''}

sources = ['turbolinux%(version_major)s%(version_minor)s.tar.gz']

sanity_check_paths = {
    'files': ['bin/x86_64-unknown-linux-gnu_mpi/aoforce'],
    'dirs': ['bin', 'basen', 'perlmodules', 'scripts'],
}

prepend_to_path = {'scripts'}

modextravars = {'TURBODIR': '%(installdir)s',
                'TURBOMOLE_SYSNAME': 'em64t-unknown-linux-gnu', # FIXME: should 
come from scripts/sysname
                'MOLE_CONTROL': '%(installdir)s/MoleControl_2.5',
}

moduleclass = 'chem'


######################################################################

However, the binaries are not directly under 'bin', but in the
subdirectories shown below:

[build@admin bin]$ tree -L 1
.
├── em64t-unknown-linux-gnu
├── em64t-unknown-linux-gnu_mpi
├── em64t-unknown-linux-gnu_smp
├── x86_64-unknown-linux-gnu
├── x86_64-unknown-linux-gnu_mpi
└── x86_64-unknown-linux-gnu_smp

What is the standard way of tweaking the PATH variable in such a case?

Cheers,

Loris

-- 
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin         Email [email protected]

Reply via email to