On Wed, Sep 09, 2009 at 07:05:01AM -0700, William G. Scott wrote:
> I also get it on a second machine (installed into /sw instead of /sw64).  
> If I issue the command "by hand", it works (or at least there is no error 
> reported):
>
> /sw/var/lib/dpkg/info/ccpnmr-py26.postinst: line 15:   474 Segmentation 
> fault      /sw/bin/python2.6 -O /sw/lib/python2.6/site- 
> packages/ccpnmr/ccpnmr2.0/python/ccpnmr/update/UpdateAuto.py
> /sw/bin/dpkg: error processing ccpnmr-py26 (--install):
>  subprocess post-installation script returned error exit status 139
> Errors were encountered while processing:
>  ccpnmr-py26
> ### execution of /sw/bin/dpkg-lockwait failed, exit code 1
> Failed: can't install package ccpnmr-py26-2.0.7.1-1
> zsh-%
> zsh-% sudo  /sw/bin/python2.6 -O /sw/lib/python2.6/site-packages/ 
> ccpnmr/ccpnmr2.0/python/ccpnmr/update/UpdateAuto.py
> zsh-%
> zsh-%
>
> also
>
> BlockFile.so:    Mach-O 64-bit bundle x86_64
> FitMethod.so:    Mach-O 64-bit bundle x86_64
> GlHandler.so:    Mach-O 64-bit bundle x86_64
> MemCache.so:     Mach-O 64-bit bundle x86_64
> PdfHandler.so:   Mach-O 64-bit bundle x86_64
> PsHandler.so:    Mach-O 64-bit bundle x86_64
> ShapeFile.so:    Mach-O 64-bit bundle x86_64
> StoreFile.so:    Mach-O 64-bit bundle x86_64
> StoreHandler.so: Mach-O 64-bit bundle x86_64
> TkHandler.so:    Mach-O 64-bit bundle x86_64
>
> Here's everything python installed, fwiw:
>
>
> boost1.35.nopython-shlibs
> f2py-py26
> libxml2-py26
> numeric-py26
> numpy-py26
> pmw-py26
> pycairo-py26
> pycairo-py26-dev
> pygobject2-py26
> pygobject2-py26-dev
> pygobject2-py26-shlibs
> pygtk2-gtk-py26
> pygtk2-gtk-py26-dev
> pymol-py26
> python
> python26
> python26-shlibs
> scientificpython-py26
> scipy-core-py26
> scipy-py26
> system-pkgconfig-xpyb
>
>
>

Bill,
   Could you test the ccpnmr-py26 build on one of your
i386 fink installations? I would assume you would have
about the same set of python packages installed (just
to make sure that none of those are the cause).
                              Jack

>
>
> On Sep 9, 2009, at 6:29 AM, Jack Howarth wrote:
>
>> On Tue, Sep 08, 2009 at 09:36:23PM -0700, William G. Scott wrote:
>>> This worked ok on my 32-bit install, but ...
>>>
>>> Setting up ccpnmr-py26 (2.0.7.1-1) ...
>>> cd ../python/memops/c; sh linkSharedObjs
>>> cd ../python/ccp/c; sh linkSharedObjs
>>> cd ../python/ccpnmr/c; sh linkSharedObjs
>>> /sw64/var/lib/dpkg/info/ccpnmr-py26.postinst: line 15: 59735
>>> Segmentation fault      /sw64/bin/python2.6 -O /sw64/lib/python2.6/
>>> site-packages/ccpnmr/ccpnmr2.0/python/ccpnmr/update/UpdateAuto.py
>>> /sw64/bin/dpkg: error processing ccpnmr-py26 (--install):
>>> subprocess post-installation script returned error exit status 139
>>> Errors were encountered while processing:
>>> ccpnmr-py26
>>> ### execution of /sw64/bin/dpkg-lockwait failed, exit code 1
>>> Failed: can't install package ccpnmr-py26-2.0.7.1-1
>>
>> Bill,
>>   This looks like the execution of...
>>
>> /sw64/bin/python2.6 -O /sw64/lib/python2.6/site-packages/ccpnmr/ 
>> ccpnmr2.0/python/ccpnmr/update/UpdateAuto.py
>>
>> where the script /sw64/lib/python2.6/site-packages/ccpnmr/ccpnmr2.0/ 
>> python/ccpnmr/update/UpdateAuto.py
>> should be...
>>
>> from ccpnmr.update.UpdateAgent import UpdateAgent,  
>> UPDATE_SERVER_LOCATION, UPDATE_DIRECTORY, UPDATE_DATABASE_FILE
>>
>> def updateAuto(serverLocation=UPDATE_SERVER_LOCATION,
>>               serverDirectory=UPDATE_DIRECTORY,
>>               dataFile=UPDATE_DATABASE_FILE):
>>
>>  updateAgent = UpdateAgent(serverLocation, serverDirectory, dataFile, 
>> isGraphical=False)
>>  server = updateAgent.server
>>  if server:
>>      server.getFileUpdates()
>>      if not server.fileUpdates:
>>        server.getFileUpdates()
>>      if server.fileUpdates:
>>        updateAgent.installNewUpdates()
>>
>> if __name__ == '__main__':
>>
>>  updateAuto()
>>
>> This looks more like possible breakage of x86_64 python on your  
>> machine than
>> a problem with ccpnmr-py26 itself. Also, make sure that everything in
>> /sw64/lib/python2.6/site-packages/ccpnmr/ccpnmr2.0/python/memops/c
>> is built as x86_64 code according to file (although I would think
>> that would give an entirely different error).
>>                              Jack

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to