Elm 2.2 on uPort SysV/AT--Help Needed

[Tim Evans]

Now that Elm 2.2 has been released to the world, it seems time to ask
the world (or at least the uPort corner of it) for help with Elm's
Configure/installation.  This came up in testing of version 2.2, but
the Development Group couldn't focus on a single system to solve it.

Basically, the problem is that the Configure script holds a large
number of elm configuration details in memory as environment variables,
then creates Makefiles and other necessary files using them.  However,
/bin/sh on uPort SysV/AT was compiled using small model and cannot 
handle all of the variables Configure creates.  For a while there,
you could get around this by using /bin/ksh, which seems to have a
bit more room.

Along towards the end of the 2.2 development cycle, though, ksh's
variable space got exceeded.  At this point, uPort SysV/AT users will
have to hand-edit all of the necessary files in order to get Elm 2.2
to install.

What's needed here is for uPort guru's (and others) to take a look
at Configure and see if there's something which can be done to deal
with this problem--without messing up Configure for the rest of the
world, of course.  At first thought, it seems that storing all these
configuration options in a temporary file (maybe a sed script?), then
somehow using the temp file to create the Makefiles instead of juggling
all of the variables in memory.

It strikes me that uPort SysV/AT may not be the only place this problem
occurs.  Maybe someone can speak to other '286 *NIX's?  (Configure
seems to allow for VenturCOM Venix(tm)--any experience/comments with
respect to that one?)
-- 
UUCP:  ...!{rutgers|ames|uunet}!mimsy!aplcen!wb3ffv!fallst!tkevans
INTERNET:  tkevans%fallst at wb3ffv.ampr.org
OTHER: ...!attmail!fallst!tkevans
Tim Evans  2201 Brookhaven Court, Fallston, MD  21047   (301) 965-3286