🚀 go-pugleaf

I am having a problem with GNU C++ (2.2.2) on an OS/2 (2.0) system.  

I downloaded GNU C/C++  for OS/2 from ftp-os2.nmsu.edu and I have
been trying to get it going on an OS/2 system.  The un-ZOOing was
a bit sticky.  The c++ header files were from a directory with
a name like g++-include which is not a legal FAT directory name.
I was not able to un-ZOO these and since I am not using c++
and GNU-C is described as two separate compilers, one for c and
one for c++, I didn't see a problem with this.
The ZOO included a SET-VARS.CMD file that sets the
gcc, g++, lib and other environment variables.  The files seems to
do exactly what the INSTALL/README said, so I just editted it
to adjust C: to E: because GNU C is on my E drive and added the
command:

PATH=E:\GNU\BIN;%PATH%

One of the sets is SET TMP=E:/GNU/TMP, okay.  When I try to compile
the sample1 program using:
gcc -c -O sample1.c
as the make file does, GNU C responds with an I/O error on a file it
specifies as:
E:\GNU\TMP\.i
I have scanned the docs etc and see no explanation why GNU C would be
trying to create such a file in the TMP directory.  The file name
".i" is of course not a legal file name in a FAT file system (I don't
know about HPFS, I am not running it).

It may seem that the solution of going to HPFS is obvious but nowhere
does it say this is required in the docs etc.  If someone has
installed GNU C and found HPFS was necessary, let me know.  Memory
requirements make HPFS undesirable on the system I am working with.

If anyone can suggest a solution to my problem could you please send 
e-mail to me at:
malone@ecf.toronto.edu
Thanks in advance...

Matt