X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4EA93E34.5090806@cornell.edu> Date: Thu, 27 Oct 2011 07:19:16 -0400 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Problems installing Imaging-1.1.7 References: <1319707869.13043.1.camel@kare-desktop> <4EA9313F.1030307@gmail.com> In-Reply-To: <4EA9313F.1030307@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 10/27/2011 6:23 AM, Marco Atzeri wrote: > On 10/27/2011 11:31 AM, Edvardsen Kåre wrote: >> I’m not able to install Imaging-1.1.7, and I assume it has something to >> do with the Tcl/Tk dll’s > > TCL/TK is under revision, > http://cygwin.com/ml/cygwin-apps/2011-10/msg00083.html > so eventually the next version will be more friendly >> >> I’ve tried the various rebase solutions as suggested in the list (and a >> lot of googling), but no luck whatsoever. Here is the output when trying >> to run the setup script. >> >> $ python setup.py build >> running build >> running build_py >> running build_ext >> building '_imagingtk' extension >> gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall >> -Wstrict-prototypes -I/usr/include/freetype2 -IlibImaging -I/usr/include >> -I/usr/local/include -I/usr/include/python2.6 -c _imagingtk.c -o >> build/temp.cygwin-1.7.9-i686-2.6/_imagingtk.o >> unable to execute gcc: Bad address >> gcc: vfork: Resource temporarily unavailable >> error: command 'gcc' failed with exit status 1 >> >> I have successfully installed >> >> matplotlib-1.1.0 (with basemap-1.0.1, including geos) >> grib_api-1.9.9 >> >> Then I tried to follow advices through this thread: >> >> http://cygwin.com/ml/cygwin/2007-01/msg00498.html > > more than that the usage of rebaseall could help > http://cygwin.com/ml/cygwin-announce/2011-10/msg00038.html The OP could also try using the latest developer snapshot (http://www.cygwin.com/snapshots/). I think there have been some improvements in Cygwin's ability to deal with DLL collisions. Ken -- 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