Problems installing Imaging-1.1.7

Problems installing Imaging-1.1.7

[Edvardsen Kåre]

I’m not able to install  Imaging-1.1.7, and I assume it has something to
do with the Tcl/Tk dll’s

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

but no luck.

Does this look familiar to anyone or do you need more info to help me
out here?

Cheers,
Kare

Re: Problems installing Imaging-1.1.7

[Marco Atzeri]

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

>
> but no luck.
>
> Does this look familiar to anyone or do you need more info to help me
> out here?
>
> Cheers,
> Kare
>

Regards
Marco

--
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

Re: Problems installing Imaging-1.1.7

[Ken Brown]

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