Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.035 X-Spam-Evidence: '*H*': 0.93; '*S*': 0.00; 'python': 0.11; 'subject:python': 0.12; 'cc:addr:python-list': 0.15; '2.7.2': 0.16; 'ncurses': 0.16; "haven't": 0.17; 'wrote:': 0.21; 'header :In-Reply-To:1': 0.22; 'header:User-Agent:1': 0.23; 'wed,': 0.24; 'work.': 0.25; 'cc:no real name:2**0': 0.26; 'tried': 0.26; 'cc:addr:python.org': 0.27; 'seems': 0.28; "i've": 0.28; 'cc:2**0': 0.31; 'skip:/ 20': 0.33; "i'll": 0.34; 'but': 0.36; 'does': 0.36; 'too.': 0.37; 'rather': 0.38; 'david': 0.39; 'mar': 0.61; '2012': 0.69; './configure': 0.84 Date: Thu, 29 Mar 2012 13:55:42 +0300 From: Alexey Luchko User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: David Robinow Subject: Re: errors building python 2.7.3 References: <4F72FAF9.8000802@ank-sia.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: python-list@python.org X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 15 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1333018538 news.xs4all.nl 6873 [2001:888:2000:d::a6]:35886 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:22335 On 28.03.2012 18:42, David Robinow wrote: > On Wed, Mar 28, 2012 at 7:50 AM, Alexey Luchko wrote: >> I've tried to build Python 2.7.3rc2 on cygwin and got the following errors: >> >> $ CFLAGS=-I/usr/include/ncursesw/ CPPFLAGS=-I/usr/include/ncursesw/ >> ./configure > I haven't tried 2.7.3 yet, so I'll describe my experience with 2.7.2 > I use /usr/include/ncurses rather than /usr/include/ncursesw > I don't remember what the difference is but ncurses seems to work. I've tried ncurses too. It does not matter. -- Alex