Date: Thu, 13 Aug 1998 10:45:23 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Gerhard Gruber <sparhawk AT eunet DOT at>
cc: djgpp AT delorie DOT com
Subject: Re: -fxref bug?
In-Reply-To: <35d9002c.1456253@news.Austria.EU.net>
Message-ID: <Pine.SUN.3.91.980813104505.2812G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Wed, 12 Aug 1998, Gerhard Gruber wrote:

> And this is a sample compiled with DJGPP on DOS/W95:
> FIL d:/bc/srcparse/test.cpp d:/bc 0
> FIL d:/bc/d:/gnu/include/stdio.h d:/bc 0
> 
> As you can see, in DJGPP the compilepath is appended before the include
> filepaths whereas this is not the case on UNIX systems. Now I wonder if this
> is intentional (why?) or if this is a bug?

Seems like a bug to me, especially since the path name in second line
is obviously garbled.

Many Unix-born programs assume that any file name which doesn't begin
with a slash is a relative file name.  Seems like this is another case
of such lossage.  (When porting a package, I usually grep the entire
source tree for strings like '/' and "/", just to hunt down all these
cases.)

Would you please consider locating this bug in the GCC sources and
posting a patch?  Thanks in advance.