X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f Message-ID: <427667F3.D20CF12E@yahoo.com> From: CBFalconer Organization: Ched Research http://cbfalconer.home.att.net X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: gcc -MM output References: <42764B12 DOT 8495F94D AT yahoo DOT com> <3dn2daF6tmbfpU1 AT news DOT dfncis DOT de> <200505021631 DOT j42GVq7P007619 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 89 Date: Mon, 02 May 2005 18:14:50 GMT NNTP-Posting-Host: 12.76.137.254 X-Complaints-To: abuse AT worldnet DOT att DOT net X-Trace: bgtnsc04-news.ops.worldnet.att.net 1115057690 12.76.137.254 (Mon, 02 May 2005 18:14:50 GMT) NNTP-Posting-Date: Mon, 02 May 2005 18:14:50 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com DJ Delorie wrote: > >> To allow the DJGPP port of GCC and DJGPP itself (libc & friends) >> to be independent of each other. djgpp.ver is the link between >> the two that tells GCC what version of DJGPP is used. > > I think the question is, why is -MM listing it, since -MM isn't > supposed to list "system" headers. Exactly. [1] c:\c\id2id\2.0>gcc -v -MM id2id.c Reading specs from c:/djgpp/lib/gcc-lib/djgpp/3.21/specs Configured with: /devel/gnu/gcc/3.2/gnu/gcc-3.21/configure i586-pc-msdosdjgpp -- prefix=/dev/env/DJDIR --disable-nls Thread model: single gcc version 3.2.1 c:/djgpp/lib/gcc-lib/djgpp/3.21/cpp0.exe -lang-c -v -MM -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=1 -D__GXX_ABI_VERSION=102 -D__MSDOS__ -D__GO32__ -D__DJGPP__=2 -D__unix__ -D__MSDOS__ -D__GO32__ -D__DJGPP__=2 -D__unix__ -Asystem=msdos -Asystem=unix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i586__ -D__tune_pentium__ -DMSDOS -DGO32 -DDJGPP=2 -Dunix -remap -imacros c:/djgpp/lib/gcc-lib/djgpp/3.21/djgpp.ver id2id.c GNU CPP version 3.2.1 (cpplib) (80386, BSD syntax) ignoring nonexistent directory "c:/djgpp/djgpp/include" #include "..." search starts here: #include <...> search starts here: c:/djgpp/lib/gcc-lib/djgpp/3.21/include c:/djgpp/include End of search list. id2id.o: id2id.c c:/djgpp/lib/gcc-lib/djgpp/3.21/djgpp.ver hashlib.h I suspect djgpp.ver is in the wrong location. It should be in c:/djgpp/lib/gcc-lib/djgpp/3.21/include instead of c:/djgpp/lib/gcc-lib/djgpp/3.21 But then how is it ever being #included at all? -E does showup the djgpp specific defines. Further results: [1] c:\c\id2id\2.0>gcc -MM empty.c empty.o: empty.c c:/djgpp/lib/gcc-lib/djgpp/3.21/djgpp.ver [1] c:\c\id2id\2.0>gcc -E -dM -c empty.c #define __HAVE_BUILTIN_SETJMP__ 1 #define __unix__ 1 #define unix 1 #define __i386__ 1 #define __SIZE_TYPE__ long unsigned int #define __GNUC_PATCHLEVEL__ 1 #define __DJGPP 2 #define __USER_LABEL_PREFIX__ _ #define __tune_pentium__ 1 #define __STDC_HOSTED__ 1 #define __MSDOS__ 1 #define DJGPP 2 #define __WCHAR_TYPE__ short unsigned int #define __DJGPP__ 2 #define __WINT_TYPE__ int #define __GNUC__ 3 #define __tune_i586__ 1 #define __DJGPP_MINOR__ 3 #define __GXX_ABI_VERSION 102 #define __GO32__ 1 #define i386 1 #define GO32 1 #define __GNUC_MINOR__ 2 #define DJGPP_MINOR 3 #define __STDC__ 1 #define __PTRDIFF_TYPE__ int #define MSDOS 1 #define __DJGPP_MINOR 3 #define __REGISTER_PREFIX__ #define __NO_INLINE__ 1 #define __i386 1 #define __VERSION__ "3.2.1" -- "If you want to post a followup via groups.google.com, don't use the broken "Reply" link at the bottom of the article. Click on "show options" at the top of the article, then click on the "Reply" at the bottom of the article headers." - Keith Thompson