Running rbutil 1.2.4 on Mac OS X 10.5.8 fails with "Dyld Error"

[strangefeatures]

Has anyone else experienced this? I can't run the new rbutil on OS X. I haven't had a problem with previous builds. When I try and open the extracted app, I get a dialog saying "The application rbutilqt quit unexpectedly" (even after downloading it again). If I go into the error report, I get the following:

Code: [Select]

Process:         rbutilqt [13030]
Path:            /Applications/rbutilqt.app/Contents/MacOS/rbutilqt
Identifier:      com.rockbox.rbutil
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [121]

Interval Since Last Report:          7135666 sec
Crashes Since Last Report:           2612
Per-App Interval Since Last Report:  286 sec
Per-App Crashes Since Last Report:   6

Date/Time:       2010-02-06 17:30:09.556 -0800
OS Version:      Mac OS X 10.5.8 (9L31a)
Report Version:  6
Anonymous UUID:  90A6EF7A-A92A-44D6-93DC-9C8BFCC88F33

Exception Type:  EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread:  0

Dyld Error Message:
  Library not loaded: @executable_path/../Frameworks/libusb-0.1.4.dylib
  Referenced from: /Applications/rbutilqt.app/Contents/MacOS/rbutilqt
  Reason: no suitable image found.  Did find:
/Applications/rbutilqt.app/Contents/MacOS/../Frameworks/libusb-0.1.4.dylib: unknown required load command 0x80000022
/Applications/rbutilqt.app/Contents/MacOS/../Frameworks/libusb-0.1.4.dylib: unknown required load command 0x80000022

I'm a little surprised this hasn't happened for anyone else, as it's very reliably reproducible for me.

Version 1.2.3 runs without issues (or at least loads up OK - I haven't tried installing with it for a while)

[bluebrother]

Has anyone else experienced this? I can't run the new rbutil on OS X.

Ok, I've checked this problem. It turns out that something strange happens when creating the dmg image -- something insists on inserting the libusb dylib, even if it's linked statically. And even worse, it inserts the wrong version of libusb -- the one inserted looks like the binary for OS X 10.6, which obviously won't run on older versions.

Can you try if the zipped application bundle from this url works? Strangely otool reports the libusb issue only when creating a dmg image from that.

I'm a little surprised this hasn't happened for anyone else, as it's very reliably reproducible for me.

Oh, the reason is simple: the number of OS X users of Rockbox Utility seems to be rather limited. Also, the binary is now built on a different machine, and its build on Snow Leopard. Which makes it possible to fail by inserting libraries that are simply too new. And as the only Mac I've got around is running SL I have no way to check against older versions (and there are no other developers actively working on OS X).

[strangefeatures]

Can you try if the zipped application bundle from this url works? Strangely otool reports the libusb issue only when creating a dmg image from that.

Awesome - that one seems to work fine (at least to start up and point it to my ipod - I haven't installed anything yet). Thanks.

Andy

[bluebrother]

Awesome - that one seems to work fine (at least to start up and point it to my ipod - I haven't installed anything yet). Thanks.

Good to hear. No idea what happens with that dmg creation, I'll look into it later. We can always fallback to application bundles for distribution, but it's a bit annoying -- our build scripts *just* got into shape

[chrisspelberg]

I can build the Leopard 32-bit version of the application here.

[keithbowden]

This could be the same bug as I found in the 1.2.4 Windows version.

Try running 1.2.3 instead. Keith Bowden

[bluebrother]

This could be the same bug as I found in the 1.2.4 Windows version.

No, it's not. It's not even related. It's a problem with building the dmg image, it has nothing to do with building Rockbox Utility itself.

Try running 1.2.3 instead. Keith Bowden

Which has a noticable amount of issues on OS X that have been fixed. And, as strangefeatures reported, the application bundle I linked does work, so why use a version that is outdated and has known issues (which can result in various failures during installation).