sage 3.2.3 os x 10.5 extension loading...

[Simon Beaumont]

Can anyone cast any light on this for me?

This is OOB sage python
____________________

00:41 chi:lib.macosx-10.3-i386-2.5 504\> sage --version
Sage Version 3.2.3, Release Date: 2009-01-05

00:41 chi:lib.macosx-10.3-i386-2.5 505\> sage -python
Python 2.5.2 (r252:60911, Jan 6 2009, 19:03:06)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import _cublas
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: dlopen(./_cublas.so, 2): Symbol not found:
__cg_png_create_info_struct
Referenced from: /System/Library/Frameworks/
ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/
Versions/A/ImageIO
Expected in: /Applications/sage/local/lib//libPng.dylib

>>>

System python - looks good (and it works)
____________
00:42 chi:lib.macosx-10.3-i386-2.5 506\> /usr/bin/python
Python 2.5.1 (r251:54863, Jan 13 2009, 10:26:13)
[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import _cublas
>>> ^D

(Now this extension was built using the sage -python and I have it
working fine on another box with sage python but a hand cranked
framework python based sage from 3.1.1 )

[seb]

Ok I'll rephrase that: Is there another version of sage that I should
be using?
Something I can do to fix this?

[seb]

I take it from the resounding silence that this is not fixed on OS X -
I read some other thread about this but seems like OS X is a PITA once
again. Is there any hope? Do I give up now? Can I delete libPng.dylib?
Help please!

[William Stein]

Unfortunately, our resident expert on this sort of problem (Michael
Abshoff) has the flu right now.

You can certainly try deleting/moving libPng.dylib...

-- William

[seb]

Sorry to hear that Michael has the 'flu.

I renamed the linPng.dylib - and the problem is side stepped. How
dependant is sage on this library?
Can we live without it? What about a dummy library that provides the
required symbol.

You guys do a fantastic job of sorting all this DLL hell out.


Thanks

[Georg S. Weber]

Hi,

AFAIK, the patch at trac #5217 (and other paches mentioned there)
should have resolved this long standing "OS X libpng" annoyance ---
all that went into Sage 3.3rc1. I'd propose to wait until Sage 3.4
binaries are out, or to download and build Sage 3.3 from source (which
is pretty forward --- but for 3.3 no binaries were/are provided for
download).

Hopefully Michael takes his time to really recover, best wishes!!!

Cheers,
gsw

[mabshoff]

On Mar 6, 11:29 am, "Georg S. Weber" <GeorgSWe...@googlemail.com>
wrote:

> Hi,
>
> AFAIK, the patch at trac #5217 (and other paches mentioned there)
> should have resolved this long standing "OS X libpng" annoyance ---
> all that went into Sage 3.3rc1. I'd propose to wait until Sage 3.4
> binaries are out, or to download and build Sage 3.3 from source (which
> is pretty forward --- but for 3.3 no binaries were/are provided for
> download).

Yeah, the issue is fixed in Sage 3.3 since we now link against
libpng12 instead of libpng to avoid symbol collisions with Apple's
IOKit.

> Hopefully Michael takes his time to really recover, best wishes!!!
>
> Cheers,
> gsw

Cheers,

Michael

[seb]

On that basis I might download 3.3 sources and go for a build if I
encounter any consequences of removing the lib.
Otherwise I'll wait for a binary release.

Cheers,

Simon