X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEALvBhkrUnw4U/2dsb2JhbADRJoQZBYFNbA Message-ID: <4A8724A0.3070307@bobcowdery.plus.com> Date: Sat, 15 Aug 2009 22:12:00 +0100 From: Bob Cowdery User-Agent: Thunderbird 2.0.0.22 (X11/20090608) 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> <4A86FF67 DOT 2050103 AT gmail DOT com> In-Reply-To: <4A86FF67.2050103@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: 998f7d727bd123f84db135a9adc3cf46 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave Thank you very much. I shall not forget -v now. It told me straight away that I had stupidly forgotten to install the cygwin gcc but did have MinGW gcc on the path which of course only understands Windows paths. Regards Bob Dave Korn wrote: > 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 > > -- 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