Oops. I have my fink set to update with launchd and didn't catch the  
small version number difference when I checked before installing. I  
thought it updated already today.

Version 1002 builds and runs perfectly! Yeah!

Cheers,
Michelle Gill


On May 9, 2008, at 6:22 PM, Jack Howarth wrote:

> Michelle,
>   You are still building pymol-py25-1.0r2-1001 and not
> the newer pymol-py25-1.0r2-1002. Make sure you have
> fink unstable enabled in /sw/etc/fink.conf and do
> a 'fink selfupdate-cvs' to pull down the latest
> info and patch for pymol-py before you try to rebuild
> pymol-py25 again.
>               Jack
>
> On Fri, May 09, 2008 at 05:35:57PM -0500, Gill Michelle wrote:
>> Unfortunately, I still get the same error--see below. If I can  
>> provide more
>> info, let me know.
>>
>> Michelle Gill
>>
>> gcc  -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
>> -I/sw/include/python2.5 -I/sw/include/python2.5  -I/sw/include  -c
>> ././ExtensionClass.c -o ./ExtensionClass.o
>> ././ExtensionClass.c: In function 'initializeBaseExtensionClass':
>> ././ExtensionClass.c:1542: warning: passing argument 2 of
>> 'PyMapping_HasKeyString' discards qualifiers from pointer target type
>> ././ExtensionClass.c:1553: warning: passing argument 3 of  
>> 'newCMethod'
>> discards qualifiers from pointer target type
>> ././ExtensionClass.c:1553: warning: passing argument 6 of  
>> 'newCMethod'
>> discards qualifiers from pointer target type
>> ././ExtensionClass.c:1561: warning: passing argument 3 of  
>> 'newCMethod'
>> discards qualifiers from pointer target type
>> ././ExtensionClass.c:1561: warning: passing argument 6 of  
>> 'newCMethod'
>> discards qualifiers from pointer target type
>> ././ExtensionClass.c:1570: warning: passing argument 2 of
>> 'PyMapping_SetItemString' discards qualifiers from pointer target  
>> type
>> ././ExtensionClass.c:1580: warning: passing argument 2 of
>> 'PyMapping_GetItemString' discards qualifiers from pointer target  
>> type
>> ././ExtensionClass.c:1583: warning: assignment discards qualifiers  
>> from
>> pointer target type
>> ././ExtensionClass.c: At top level:
>> ././ExtensionClass.c:2870: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2872: warning: 'intargfunc' is deprecated
>> ././ExtensionClass.c:2872: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2873: warning: 'intargfunc' is deprecated
>> ././ExtensionClass.c:2873: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2874: warning: 'intintargfunc' is deprecated
>> ././ExtensionClass.c:2874: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2875: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2876: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c:2988: warning: initialization from incompatible
>> pointer type
>> ././ExtensionClass.c: In function 'CopyMethods':
>> ././ExtensionClass.c:3267: warning: passing argument 2 of  
>> 'PyDict_Next'
>> from incompatible pointer type
>> ./ExtensionClass.o   -o ./ExtensionClass.so
>> make[2]: execvp: ./ExtensionClass.o: Permission denied
>> make[2]: *** [ExtensionClass.so] Error 127
>> make[1]: *** [make-modules] Error 2
>> make: *** [unix] Error 2
>> ### execution of make failed, exit code 2
>> Removing runtime build-lock...
>> Removing build-lock package...
>> /sw/bin/dpkg-lockwait -r fink-buildlock-pymol-py25-1.0r2-1001
>> (Reading database ... 15577 files and directories currently  
>> installed.)
>> Removing fink-buildlock-pymol-py25-1.0r2-1001 ...
>> Failed: phase compiling: pymol-py25-1.0r2-1001 failed
>>
>> On May 9, 2008, at 3:57 PM, Jack Howarth wrote:
>>
>>> Michelle and Michael,
>>>  Try the new pymol-py-1.0r2-1002 packaging in fink 10.4/10.5
>>> unstable. I've hacked around the problem of the python from
>>> the python2.5 package incorrectly generating the Makefile in
>>> contrib/modules. The package should build fine now although
>>> we still need to figure exactly what change was made recently
>>> in python25 which caused this problem. I am certain that
>>> pymol-py25 was building fine just a few weeks back (immediately
>>> after python25 was updated to 2.5.2).
>>>             Jack


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Fink-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to