X-Envelope-From: ultan AT cix DOT compulink DOT co DOT uk Date: Sun, 16 Apr 2000 09:25 +0100 (BST) From: ultan AT cix DOT compulink DOT co DOT uk (Ultan Henry) Subject: Environment variables To: djgpp AT delorie DOT com Cc: ultan AT cix DOT compulink DOT co DOT uk Message-Id: X-Ameol-Version: 2.52.2000, Windows 98 4.10.1998 ( ) Reply-To: djgpp AT delorie DOT com I've built an arm-elf cross-compiler built and hosted on DJGPP. The tools are installed in 'C:\armtools' and work correctly when run from other directories on the C drive. However, there is a problem if I try to run the compilers while in a directory on another disk. In this case, no path seems to be found to the 'crt0.o' file for linking. The DJGPP environment variable is pointing to a file containing the following: ------------------- DJDIR=%:/>DJGPP% +USER=dosuser +LFN=y COMPILER_PATH=%DJDIR%\arm-elf\bin\ GCC_EXEC_PREFIX=%DJDIR%\lib\gcc-lib\ C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/include LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib ------------------- Without setting GCC_EXEC_PREFIX as shown, the compiler uses its built-in specs and the CPP seems to be called recursively with a ever increasing (and repeated) list of options. Again, this only happens when calling the compilers from a drive other than the C drive on which they are installed which I assume is due to the use of relative paths. Is there a way to allow the 'crt0.o' file to be found correctly, or perhaps this is due to a mistake in the configuration used to build the compilers (shown below)? Any help would be appreciated! Compiler configuration: configure --verbose \ --disable-nls \ --with-gnu-as \ --with-gnu-ld \ --target=arm-elf \ --disable-shared \ --host=i386-pc-msdosdjgpp \ --with-cpu=strongarm \ --with-newlib \ --with-local-prefix=/armtools/arm-elf \ --with-gxx-include-dir=/armtools/lang/cxx \ --prefix=/armtools