Date:	Mon, 7 Nov 94 05:15:39 JST
From:	Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
To:	"DJGPP, mailing, list"@shako.sk.tsukuba.ac.jp,
	DJGPP <DJGPP AT Sun DOT SOE DOT Clarkson DOT edu>
Subject:	GCC search paths - my bad

I'm clearly going crazy, because I always assume that GCC knows more
about what it's doing than I do.  So I checked everything in that last
post twice.  A couple of reboots later, make and GCC work as
advertised, the global path comes *after* COMPILER_PATH, I can use the
method I suggested in my previous post, so you can all breathe easily.
    Probably it's important only to me personally, but I still don't
have a working GS 'cause I can't round up enough virtual memory to
link it.  But I'm going to check this "bug" out FIVE times before I
post.  I bet that's a *real* relief.
    --Steve

- Raw text -