X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4A86FF67.2050103@gmail.com>
Date:	Sat, 15 Aug 2009 19:33:11 +0100
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Compiling problem
References:	<4A85C9DB DOT 5010903 AT bobcowdery DOT plus DOT com> <4A86F623 DOT 3070204 AT bobcowdery DOT plus DOT com>
In-Reply-To:	<4A86F623.3070204@bobcowdery.plus.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

Bob Cowdery wrote:
> Either I'm too impatient, the question is too trivial for people to
> bother with or too complex or lacking information to be answerable. As
> I've not posted to this group before and have hardly used Cygwin I've no
> idea which of the above is true. Anybody... please.

  Complex and lacking information.  I've never heard of Cython or Pyrex, but
if you could manage to cut your failing compile down to a really simple
testcase that anyone can reproduce, you'll get a lot more help a lot quicker.

>> part of the compile. I installed Pyrex and have tried to build a
>> minimal Python module but gcc can't seem to locate the python header
>> files. They are there and the -I points to the right place
>> '-I/usr/include/python2.5'. In that directory is Python.h which it
>> can't find.

  Copy and paste the failing command line from your build logs into a bash
shell, adding the "-v" flag.  If the list of search paths that shows you
doesn't help, try making a copy of the failing .c file, but snip out
everything after the #include statements at the top, and try compiling that
(with the same command-line, just change the name of the .c file it mentions).
 If that also doesn't work, post the commandline and the cut-down .c file here.

    cheers,
      DaveK



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -