|
From: R.K. O. Ph.D. <rk...@ow...> - 2001-04-05 20:15:13
|
> > I just re-joined this list after about 5 years off of it. I noticed > that on www.modules.org that things appear to have been revived, but > that document is 2 years old, so I'm not so sure. > > We use the modules infrastructure to manage our shell environments > here at Morgan Stanley. I brought the code along with me when I left > my previous employer back in 1992, and it has been very, very stable > for the past 9 years. > > Now, I'm trying to build modulecmd on Linux, and getting stuck on: > > gcc -c -I.. -I. -I/ms/dist/tcl/VERS/8.0/include -O2 utility.c > utility.c:488: initializer element is not constant > > Line 488 seems pretty innocuous: > > static FILE* aliasfile = stdout; > > But stdout is no longer a constant on Linux, so.... compile error. > > This problem is for the 2.2 release, and I see the same problem with > 3.0 as well. The platform is: > > (system:anyuser/wpm/wpm) uname -a > Linux mglnxcs01 2.2.14-5.0smp #1 SMP Tue Mar 7 21:01:40 EST 2000 i686 unknown > > I would be shocked if I'm the first person to build this on Linux. > What you probably grabbed was the 3.0pre version. There has been some work on the 3.0 version which can be grabbed from ftp://modules.sourceforge.net/pub/modules As mentioned elsewhere, it's pretty stable, with a couple of caveats. It compiles with almost any version of Tcl (no need to have access to the Tcl internal headers). It uses the GNU configure script, and has much more capability. And has a GPL. Some folks are really married to the 2.2 version though and can't tolerate any gotcha's that the 2.2 version handled well (like deep modulefile directories). Any code patches will be gratefully accepted. Your mileage may vary, R.K. +-----------------------+----------------------------------+ | R.K.Owen,PhD | rk...@ow... (408)377-5373 | | KooZ Software | | | NERSC/LBNL | rk...@ne... (510)486-7556 | +-----------------------+----------------------------------+ |
