X-Envelope-From: ultan AT cix DOT compulink DOT co DOT uk
Date: Sun, 16 Apr 2000 14:40 +0100 (BST)
From: ultan AT cix DOT compulink DOT co DOT uk (Ultan Henry)
Subject: Re: Environment variables
To: eliz AT is DOT elta DOT co DOT il
Cc: ultan AT cix DOT compulink DOT co DOT uk, djgpp AT delorie DOT com
Message-Id: <memo.397209@cix.compulink.co.uk>
X-Ameol-Version: 2.52.2000, Windows 98 4.10.1998 ( )
Reply-To: djgpp AT delorie DOT com

In-Reply-To: <Pine DOT SUN DOT 3 DOT 91 DOT 1000416131808 DOT 3948C-100000 AT is>
> The problem of infinite recursion in cpp invocation and the problem of 
> finding the crt0.o file are two different problems.

Unfortunately, in my case I either seem to get one of these problems or 
the other depending on which solution I try!

Without setting the GCC_EXEC_PREFIX or COMPILER_PATH variables, the 
compiler does seem to use the correct built-in specs for 
my cross-development configuration. However, using the -v option shows 
that these seem to be applied recursively to invocations of CPP until DOS 
memory is exhausted.

> In particular, neither GCC_EXEC_PREFIX nor COMPILER_PATH are relevant 
> to where GCC looks for crt0.o.

According to the GCC documentation, the GCC_EXEC_PREFIX is used for 
finding files such as 'crt0.o' during linking. Is this documentation out 
of date?

> I suggest to reconfigure with prefix=c:/armtools/.. or /dev/c/armtools

I was hoping to avoid building the tools with an absolute path so that 
they could be installed on different drives. I believe the DJGPP DOS 
binaries are configured with relative paths but seem to work correctly 
when invoked from another drive.