Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!munnari.oz.au!ariel!ucsvc.ucs.unimelb.edu.au!lu!ecsgrt
From: ECSGRT@lure.latrobe.edu.au (Geoffrey Tobin, Electronic Engineering)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: v10i111: dj1bin, GNU C and C++ for 386/DOS (part 01/36)
Message-ID: <5058@lure.latrobe.edu.au>
Date: 14 Feb 91 03:19:49 GMT
References: <3114@sixhub.UUCP> <NELSON.91Feb11113723@sun.clarkson.edu> <1991Feb11.233356.18585@sj.ate.slb.com>
Organization: VAX Cluster, Computer Centre, La Trobe University
Lines: 72

In article <1991Feb11.233356.18585@sj.ate.slb.com>, poffen@sj.ate.slb.com (Russ Poffenberger) writes:
> 
> I just wish that it could co-exist with memory managers like qemm.

Is this why XMDISK and DJC (previously) seized my system?

I (only) suspect that MS WINDOWS 3.0 also may clash with DJ's gcc.


SOME GOOD NEWS:

When I replaced the autoexec.bat and *.sys files for WINDOWS by
those for the Basic DOS system, and rebooted, then DJ's gcc worked
without a hitch.

I've set up the DOS env. vars as follows:

PATH=...;F:\DJC\BIN
gccbin=f:/djc/bin
gccinc=f:/djc/include
gcclib=f:/djc/lib
gcctmp=f:/tmp

My config.sys file contains:

files= 30
buffers = 8
FCBS=10,8
device=c:\system\rmdrive.sys
device=c:\system\dmdrvr.bin
device=c:\system\dfimouse.sys


SOME DIAGNOSTICS FOR THE (TROUBLESOME) WINDOWS SETUP:

The CONFIG.SYS under the ancien regime was:

files= 30
FCBS=10,8
device=c:\system\rmdrive.sys
device=c:\system\dmdrvr.bin
device=C:\system\himem.sys
buffers = 8
device=C:\WINDOWS\smartdrv.sys 78
device=C:\WINDOWS\ega.sys

When I typed just "gcc", it rightly said:
	F:\DJC\BIN\GCC.EXE: No input files specified.
But when I typed "gcc hello.c", or typed "ar", for example, then my
system seized up.

Rebooting required the RESET button (ctrl-alt-del did nothing).

Then I found in F:\TMP the file CCAA_AAA.GP, which contained

-undef
-D__GNUC__
-Dunix
-Di386
-D__unix__
-D__i386__
hello.c
f:/tmp/ccAA_AAA.cpp

I've seen the -D compile switches in the makefiles for gcc.

My guess is that ccaa_aaa.gp and ccaa_aaa.cpp are the temporary
files for the gcc frontend and cpp passes of the compiler,
respectively.  Each time gcc crashed on hello.c, ccaa_aaa.gp had
the same name (so it wasn't randomized :-)).  Once the system
was setup right for gcc to work, the temporary files didn't stay
around.