id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc
615	mpich2.module	chan@…		"

{{{


The offending file is src/packaging/envmods/mpich2.module.in.
mpich2.module shouldn't be installed $datadir in its current form,
e.g. commenting out the install line in the envmods/Makefile.sm
for 1.1 release.

A.Chan

----- ""Anthony Chan"" <chan@mcs.anl.gov> wrote:

> Actually prepended PATH is wrong, @datadir@ is ${prefix}/share,
> since prefix is not defined in the module, the file is
> totally useless.
>
> ----- chan@mcs.anl.gov wrote:
>
> > I notice in mpcih2-1.1rc1's install dir, $datadir, has a file
> > called mpich2.module which has the following line.
> >
> > *********************************
> > #%Module 1.0
> > #
> > #  MPICH2 module for use with 'environment-modules' package:
> > #
> > prepend-path            PATH            @datadir@/bin
> > *********************************
> >
> > 1st, the file is incomplete.
> >      It needs at least to update MANPATH and LD_LIBRARY_PATH
> >      if it is a shared library build.
> >
> > 2nd, I think the file should be in $sysconfdir instead
> >      of $datadir since .module file is a configuration
> >      file.
> >
> > 3rd, this module file format seems like one particular favor of
> > modulefiles,
> >      should there some tests in configure to check if user
> environment
> >      has ""module"" command before even configure/build the .module
> file
> > ?
> >      I have been using cmod on my laptop for years, it is different
> > from
> >      Tcl/tk based modulefiles....
> >
> > 4th, should the path to the module files be appended with version of
> >      mpich2 or even compiler used.... ?
> >
> > A.Chan
}}}"	bug	closed	major		mpich2	fixed