ML> Advice?

Mike:

First, I had to make one change to the install script to load REXXUTIL.DLL.
 I edited the file name to include the full path of where to find it.

Then I played arround, with multiple runs of install.cmd.

Trying to install to H: causes problems.  The install.cmd uses some
relative paths that don't work when trying to put emx in H:\EMX....  :(

Final solution....

(a) Ran install.cmd and told it to install in H:\GCC
(b) Allowed install.cmd to make that directory.
(c) Let install.cmd complete.
(d) moved H:\GCC\EMX down to H:\EMX
(e) Edited h:\emx\bin\setgcc.cmd so that H:\GCC becomes H:EMX.
(f)  Ran H:\EMX\BIN\EMXREV.EXE to find out current library levels.  [Saved
a copy by using 'H:\EMX\BIN\EMXREV.EXE 1>EMXREV.OLD'.]
(g) Edited config.sys to change all C:\EMX references to H:\EMX.
(h) Rebooted the system.
(i) Ran H:\EMX\BIN\EMXREV.EXE to see the new library levels.  [Also saved a copy.)

I found that I only had the EMX runtime support installed and not the
development EMX environment installed.  By switching to H:\EMX, I got all
of the EMX development (including runtime) support.  In my case, the
runtime support I had on C: was the same level of code that was installed
on H:, so I should be ok.

With this, GCC just works.  I don't have to run the setgcc.cmd script to
use the compiler.  gcc hello.c produced hello.exe, and you know what that
prints....  

[Ok, so hello.c is a file I wrote up, but you know the standard code for
this.... ]

I haven't tried anything more complicated yet, but in playing around, I do
see that make won't work without adding h:\emx\make to a search path or
two.  If you do that in config.sys, you will get a number of *nix based
commands (make, chmod, cp, etc.), and I don't know if there is any issues
with that....

So....  Take care.....

Bob Jones, 1:343/41


--- Maximus/2 3.01