From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Tue, 16 May 2000 18:53:01 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Fw: DJGPP config changes part 2 of 2
Message-ID: <3921990D.15917.132573@localhost>
In-reply-to: <200005162121.RAA20131@indy.delorie.com>
References: <392113EB DOT 12560 DOT 1376E8 AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Ugh!  Why can't Unix programmers learn that file names are not
> strings, and cannot be taken apart at will and compared literally??

The function does take into account drive names and the function is only used 
once to set the exec prefix which is what tells gcc where to look for the 
compiler. 

> You *are* aware that this will all fall apart if the value of DJDIR
> changes while GCC runs, yes?  Yes, I know that currently there's no
> such danger, but it's a trap waiting for its victim...

Already fixed.
 
> How important is the code that computes relative file names?

See above. I should also note that the code that only canonicalizes the paths 
stored in gcc.c that gcc needs to find the compiler, assembler, linker, 
include files, etc. Any other paths are left alone. So with a command line 
'gcc -c /dev/env/DJDIR/sourcecode.c', the given filename is not 
canonicalized. 

Mark