0
0

Just trying to get things running on iPhone. Sound works fine on a 3.1.x device, though it’s taking RAM we could use elsewhere :-)

But I ran on a 2.2.1 device, and get a crash FMOD_OS_Time_GetNS. There’s also some console output

[code:2stnq7yl]dyld: lazy symbol binding failed: Symbol not found: ___floatundidf
Referenced from: /var/mobile/Applications/A7F8ED9D-EC25-401A-95A9-4B9C127C0103/MyApp.app/MyApp
Expected in: /usr/lib/libgcc_s.1.dylib

dyld: Symbol not found: ___floatundidf
Referenced from: /var/mobile/Applications/A7F8ED9D-EC25-401A-95A9-4B9C127C0103/MyApp.app/MyApp
Expected in: /usr/lib/libgcc_s.1.dylib

dyld: lazy symbol binding failed: Symbol not found: ___floatundidf
Referenced from: /var/mobile/Applications/A7F8ED9D-EC25-401A-95A9-4B9C127C0103/MyApp.app/MyApp
Expected in: /usr/lib/libgcc_s.1.dylib

dyld: Symbol not found: ___floatundidf
Referenced from: /var/mobile/Applications/A7F8ED9D-EC25-401A-95A9-4B9C127C0103/MyApp.app/MyApp
Expected in: /usr/lib/libgcc_s.1.dylib[/code:2stnq7yl]

I wonder if it’s sensitive to which version of GCC is used?

  • You must to post comments
0
0

When we build we always use the latest SDK / Xcode (hence compiler), with the target set to 2.0 to ensure all versions are supported. Can you confirm you are using the latest to build also?

  • You must to post comments
0
0

Looks like it’s FMOD 4.26. Given we had this before Xcode 3.2 came out, it must use slightly different compilers. I think we switched to GCC 4.2 when we switched our Macs to Snow Leopard.

So far, our app (with FMOD statically linked) works fine on 3.1.x machines, and fails on the 2.2.1 machine. Which is the situation described at http://stackoverflow.com/questions/1313 … -on-iphone though I’m not sure I get an answer there.

  • You must to post comments
0
0

So you are building with Xcode 3.2 but having problems with 2.2.1 devices running the produced binaries?

This sounds like a compiler bug to me, the compiler shouldn’t be using libs that are not available in the 2.2.1 devices. I see there is an Xcode 3.2.1 available, I’m upgrading to that now, hopefully one of the bug fixes was for this particular case.

Our next version will ship built with Xcode 3.2.1 using SDK 3.1.2.

  • You must to post comments
0
0

Call stack (from init call):

0 0x2fe01060 in __dyld_dyld_fatal_error

1 0x2fe07cb0 in __dyld__ZN4dyld14bindLazySymbolEPK11mach_headerPm

2 0x2fe15ebc in __dyld_stub_binding_helper_interface

3 0x005ce31c in FMOD_OS_Time_GetMs

4 0x005af21c in FMOD::Debug

5 0x005e6698 in FMOD::SystemI::init

6 0x005ddf68 in FMOD::System::init

I’m pretty sure our app use to work on 2.2.1 (or even 2.1.2) when building with 4.26.09 and building with sdk 3.0.

NOTE: we do not get any of the warning/errors while linking as mentioned in the original thread message.

  • You must to post comments
0
0

Thanks for the report, we are working on a solution to bring back support for 2.2.1. I’ll post back here when I have more info for you.

  • You must to post comments
0
0

This issue has been solved, the next released version for all branches will run correctly on 2.2.1.

  • You must to post comments
0
0

it’s an old bug, i am using this fix:

extern "C" double __floatundidf(unsigned long long n)
{
return (double)((long long)(n % LONG_LONG_MAX));
}

  • You must to post comments
Showing 7 results
Your Answer

Please first to submit.