Message-Id: <3.0.6.32.19990228102616.00980540@pop.globalserve.net>
X-Sender: derbyshire AT pop DOT globalserve DOT net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Sun, 28 Feb 1999 10:26:16 -0500
To: djgpp AT delorie DOT com
From: Paul Derbyshire <pderbysh AT usa DOT net>
Subject: Re: Problem building c++ programs
In-Reply-To: <36D9649A.97E851B8@solutions2000.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990228143434 DOT 5950Z-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com

At 10:45 AM 2/28/99 -0500, you wrote:
>Here is detailed info regarding my problem building c++ programs with gcc...

Looks like this is a bona fide bogon: everything is set up correctly and it
still doesn't work, and moreover, it works or doeasn't work based on
conditions that can't possibly affect it.

Things to look for now:
* Are you using an unusual local variant of DOS/Windows? Your country
  code means there is a fair chance you're using a variant with
  different language and possibly other, undocumented differences.
  One of those could be screwing things up in an obscure way.
* Since gxx works and gcc sometimes doesn't, there may be a corruption
  in gcc.exe; re-extract it from gcc281b.zip and see if the problem
  goes away.
* Since gxx and gcc call the same passes, cpp, cc1plus, as, and ld,
  none of those can be the problem or else gcc -lstdcxx and gxx would 
  work identically on your system, which they do not.
* Since gcc complains outputting to tester.exe but not to a.exe,
  check anything that might make those two filenames behave
  differently. Do you keep compiling to tester.exe with a previous
  tester.exe to overwrite, but not a.exe? When you compile to
  tester.exe, do you specify a drive and path, different from where
  you invoke the compiler? (Then it may be running out of space on
  that drive, but not when it makes a default a.exe in the invocation
  directory.)
* Bubblespace: are you using any disk compression? That has been
  known to introduce strange, inexplicable, and even seemingly
  impossible bogons into the filesystem. For example, a drive with
  40 megs free where any file create operation causes a spurious
  "disk full" error, and occasional sporadic file vanishings.
* If all else fails, chalk it up to Winblows and M$.

-- 
   .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
-()  <  circles, and bark is not smooth, nor does lightning travel in a
   `*'  straight line."    -------------------------------------------------
        -- B. Mandelbrot  |http://surf.to/pgd.net
_____________________ ____|________     Paul Derbyshire     pderbysh AT usa DOT net
Programmer & Humanist|ICQ: 10423848|