>
> Gintautas Grigelionis wrote:
>
> > Well, I built modules on vanilla tcl/tk 8.3.3 and tclx 8.3.0, all with
> > workshop 5.0 on solaris 2.6
> >
> > It's a pretty much standard stuff, the null module is
> > [snip]
> >
> > It does the job, producing
> >
> > setenv _LMFILES_ '/usr/share/lib/modules/modulefiles/null';setenv
> > LOADEDMODULES 'null';
> >
> > whether I have "" around 3.1.5 or not.
> >
> > It gets quiet when "version ..." is not the last line, e.g.
> > [snip]
> >
> > Why this stuff is position-sensitive, it beats me (apparently
> > something with the way tcl decides where a statement ends). It is
> > actually sufficient to add an empty line at the end of the original
> > modulefile.
> >
> > Thanks for all who responded,
>
> Hello, Gintautas.
>
> I modified my null modulefile, and indeed it occurs on my Linux
> system as well. It appears to be a bug.
>
> Regards,
>
> - Leo Butler
>
I've run into this problem before (and have conveniently forgotten
it) and had just gotten into the habit of adding a blank line at
the end of each modulefile.
I'll add some verbage to the PROBLEMS file regarding this specific
case. It doesn't appear to be a problem for non-Linux systems as
far as I can remember, and for Linux systems it just dumps out
the annoying error message:
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
nnn(18):ERROR:102: Tcl command execution failed: 3.1.5
but still correctly executes the modulefile.
R.K.
+------------------+---------------------+
| R.K.Owen,PhD | rk...@ow... |
| KooZ Software | Environment Modules |
| NERSC/LBNL | rk...@ne... |
+------------------+---------------------+
|