Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <937756AF9E0BDC4396C09F32D8B41F2B0B7B9F@PAUEX2KU01.ags.agere.com>
From: "Williams, Gerald S (Jerry)" <gsw AT agere DOT com>
To: cygwin AT cygwin DOT com
Subject: gcc -MM and #include <some_cygwin_package_include.h>
Date: Fri, 21 Mar 2003 16:57:09 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

I'm sure the answer to this already exists, but
googling didn't turn anything up, and I'm not the
GCC expert I wish I were. :-(

I'm using "gcc -MM" to build make dependencies. It
used to skip anything included in <>, but now it
uses some other mechanism to decide which headers
are "system". This doesn't include "system" headers
installed for the Cygwin python package, though.
Thus my #include <Python.h> results in loads of new
dependencies that didn't show up with gcc 2.95.

Is there some way these can be added to Cygwin's
list of system includes? I'm not taking sides on
whether these should be "officially" system headers
or not, but in my case I'd really like them to be.

Meanwhile, I'm looking for a workaround (-I- didn't
help). I'll poke around other lists, but I'd bet
somebody's already run into this with Cygwin. "Piss
off but have a nice day anyway" is an acceptible
response, but any web/FAQ/message/etc. references
would be highly appreciated. :-)

-Jerry

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/