aqsl on OSX 10.4

View: New views

2 Messages — Rating Filter: Alert me

aqsl on OSX 10.4

by Matthias Baas-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

when I tested Aqsis 1.6 on OSX 10.4 so far, I was only looking at the
renderer itself which worked without any problem at all.
But there is a slight problem with aqsl:

$ aqsl testShader.sl
dyld: Symbol not found: __ZNKSt9bad_alloc4whatEv
Referenced from:
/Applications/Graphics/Aqsis.app/Contents/Resources/bin/../../Frameworks/libboost_wave.dylib
Expected in: /usr/lib/libstdc++.6.dylib

Trace/BPT trap

The missing symbol is this:

$ c++filt
__ZNKSt9bad_alloc4whatEv
std::bad_alloc::what() const

Looking at the libraries:

$ otool -L
/Applications/Graphics/Aqsis.app/Contents/Frameworks/libboost_wave.dylib
/Applications/Graphics/Aqsis.app/Contents/Frameworks/libboost_wave.dylib:
@executable_path/../../Frameworks/libboost_wave.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_filesystem.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_date_time.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_thread.dylib
(compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 103.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 124.1.1)

$ otool -L /usr/lib/libstdc++.6.dylib
/usr/lib/libstdc++.6.dylib:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.3.7)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)

So does that mean aqsl was compiled on a machine that had libstdc++
v7.9.0 whereas I have v7.4.0? But don't they both claim to be compatible
with v7.0.0 so that this unresolved symbol shouldn't have happened? (or
was bad_alloc::what() added after 7.4? But then shouldn't it be recorded
in libboost_wave somewhere that it needs a higher version of libstdc++?)

- Matthias -

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Aqsis-development mailing list
Aqsis-development@...
https://lists.sourceforge.net/lists/listinfo/aqsis-development

Re: aqsl on OSX 10.4

by ALoopingIcon :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I have exactly the same problem, but with OSX 10.5.8 (plain leopard)
renderer is ok, but compiling a shader causes

dyld: Symbol not found: __ZNKSt9bad_alloc4whatEv
Referenced from: /Applications/Aqsis.app/Contents/Resources/bin/../../Frameworks/libboost_wave.dylib
Expected in: /usr/lib/libstdc++.6.dylib

thanks in advance....

p.

Matthias Baas-3 wrote:

Hi,

when I tested Aqsis 1.6 on OSX 10.4 so far, I was only looking at the
renderer itself which worked without any problem at all.
But there is a slight problem with aqsl:

$ aqsl testShader.sl
dyld: Symbol not found: __ZNKSt9bad_alloc4whatEv
Referenced from:
/Applications/Graphics/Aqsis.app/Contents/Resources/bin/../../Frameworks/libboost_wave.dylib
Expected in: /usr/lib/libstdc++.6.dylib

Trace/BPT trap

The missing symbol is this:

$ c++filt
__ZNKSt9bad_alloc4whatEv
std::bad_alloc::what() const

Looking at the libraries:

$ otool -L
/Applications/Graphics/Aqsis.app/Contents/Frameworks/libboost_wave.dylib
/Applications/Graphics/Aqsis.app/Contents/Frameworks/libboost_wave.dylib:
@executable_path/../../Frameworks/libboost_wave.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_filesystem.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_date_time.dylib
(compatibility version 0.0.0, current version 0.0.0)
@executable_path/../../Frameworks/libboost_thread.dylib
(compatibility version 0.0.0, current version 0.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 103.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 124.1.1)

$ otool -L /usr/lib/libstdc++.6.dylib
/usr/lib/libstdc++.6.dylib:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.4.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.3.7)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)

So does that mean aqsl was compiled on a machine that had libstdc++
v7.9.0 whereas I have v7.4.0? But don't they both claim to be compatible
with v7.0.0 so that this unresolved symbol shouldn't have happened? (or
was bad_alloc::what() added after 7.4? But then shouldn't it be recorded
in libboost_wave somewhere that it needs a higher version of libstdc++?)

- Matthias -

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Aqsis-development mailing list
Aqsis-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aqsis-development