X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
Date:	Sun, 10 Feb 2002 19:28:33 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	Sven Sandberg <svsa1977 AT student DOT uu DOT se>
Message-Id:	<2593-Sun10Feb2002192833+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp AT delorie DOT com
In-reply-to:	<3C6675E2.D9F792E1@student.uu.se> (message from Sven Sandberg on
	Sun, 10 Feb 2002 14:30:10 +0100)
Subject:	Re: another gcc 3.03 dependency question
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1020210135041 DOT 15572M-100000 AT is> <3C6675E2 DOT D9F792E1 AT student DOT uu DOT se>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Sun, 10 Feb 2002 14:30:10 +0100
> From: Sven Sandberg <svsa1977 AT student DOT uu DOT se>
> 
> Eli Zaretskii wrote:
> > If you indeed run "gcc -MM" (without any other switches), GCC should
> > have complained about <tmp.h> not found anywhere in the include path.
> > So something is missing in your description.
> 
> But tmp.h is in the system header directory, c:\djgpp\include\

Well, you didn't tell that in your message.  People don't normally
put random include files into c:\djgpp\include, so I thought that
file was in the same directory as tmp.c

> I don't have an earlier version here so I can't test, but I think this
> used to work with 2.95.*, i.e., it didn't produce dependencies to qouted
> include files.

Then it's probably a bug in GCC 3.0.3.

> Oh, and when I'm at it, what is this djgpp.ver thing anyway?

It defines two symbols, __DJGPP__ and __DJGPP_MINOR__, which tell
what is the version of the library you are using.  Some programs look
at the values of these variables, and conditionally compile different
code as appropriate for each library version.

> It's not
> very good to have it in dependency files which you distribute, so I
> usually sed it out. Is there any preferred way to get rid of it?

No, I don't think GCC has a way to not include such files in the
dependencies.

- Raw text -