From:	sparhawk AT eunet DOT at (Gerhard Gruber)
Newsgroups:	comp.os.msdos.djgpp
Subject:	-fxref bug?
Date:	Wed, 12 Aug 1998 21:27:36 GMT
Organization:	EUnet Austria
Lines:	38
Message-ID:	<35d9002c.1456253@news.Austria.EU.net>
NNTP-Posting-Host:	e162.dynamic.vienna.at.eu.net
Mime-Version:	1.0
NNTP-Posting-Date:	12 Aug 1998 21:28:42 GMT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I'm currently writing a classbrowser and for this I need the information
produced by the -fxref switch. Now I noticed a rather weird statement and I
wonder if this is intentional or if it is a bug.

This is a sample compiled on a hpux system with gcc:

FIL /sfa/entw/src/gui2/gru/tracer/test.cpp /sfa/entw/src/gui2/gru/tracer 0
FIL /usr/local/lib/gcc-lib/hppa1.0-hp-hpux10.20/2.7.2.1/include/stdio.h
/sfa/entw/src/gui2/gru/tracer 0

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

I don't know if you know what the fields mean from that output (I'd be
grateful for any information because I don't know what the numbers mean). The
first entry is the fully qualified sourcefilename and the second parameter is
the working directory where the compiler is called from, to compile the
source. In the second line the first entry gives the pathname of an include
file. 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?

--
Bye,
   Gerhard

email: sparhawk AT eunet DOT at
       g DOT gruber AT sis DOT co DOT at

Spelling corrections are appreciated.

- Raw text -