aMule Forum
English => Multiplatform => Mac OSX => Topic started by: Ambrose on January 02, 2006, 03:14:56 PM
-
Terminal session, attempt to open executable directly from inside package:
~ admin$ /Applications/aMule.app/Contents/MacOS/amule
dyld: /Applications/aMule.app/Contents/MacOS/amule can't open library: @executable_path/../Frameworks/libwx_base_carbonu_xml-2.7.0.dylib (No such file or directory, errno = 2)
Trace/BPT trap
-
use the one from berlios NOT sourceforge, we working on getting them to the same version again ;)
20-30min ;)
-
Thank you for your VERY fast reply.
-
The good news is that the Berlios download link and the ed2k link point to a binary that contains the dylib missing from the sourceforge package.
The not-so-good news is that the more complete binary still has a problem:
Host Name: g4.local
Date/Time: 2006-01-02 09:52:52 -0500
OS Version: 10.3.9 (Build 7W98)
Report Version: 2
Command: amule
Path: /Users/admin/Desktop/aMule-2.1.0-Mac/aMule.app/Contents/MacOS/amule
Version: ??? (???)
PID: 1493
Thread: Unknown
Link (dyld) error:
dyld: /Users/admin/Desktop/aMule-2.1.0-Mac/aMule.app/Contents/MacOS/amule Undefined symbols:
/Users/admin/Desktop/aMule-2.1.0-Mac/aMule.app/Contents/MacOS/../Frameworks/libwx_macu_core-2.7.0.dylib undefined reference to _kCGColorSpaceGenericRGB expected to be defined in Carbon
/Users/admin/Desktop/aMule-2.1.0-Mac/aMule.app/Contents/MacOS/../Frameworks/libwx_macu_core-2.7.0.dylib undefined reference to _TXNGetCommandEventSupport expected to be defined in Carbon
/Users/admin/Desktop/aMule-2.1.0-Mac/aMule.app/Contents/MacOS/../Frameworks/libwx_macu_core-2.7.0.dylib undefined reference to _TXNSetCommandEventSupport expected to be defined in Carbon
-
And you are getting that crash report while you are starting aMule? Very weird, the new binary seems to start fine on my PowerBook here.
-
Well, it turns out that aMule 2.1.0 works fine -- but only in my Macs running Tiger (10.4.3, build 8F46). It does not work (fails to launch, nothing on screen, no bouncing icon) on my Macs which are running under Panther (10.3.9, build 7W98).
-
Ah ok, that makes sense now. It's possible that Kry built the Mac binary on a Tiger machine and it therefore does not run smoothly on 10.3. For this reason, I build all my CVS binaries on 10.3 so that they are compatible with both 10.3 and 10.4.
Unfortunately, I have to leave in 30min and won't be back until very late tonight, but if things have not been worked out until then, I'll build a 2.1.0 binary on my 10.3 then and post it here.
-
This is better service than I get from companies to whom I have paid $thousands$ for software.
:baby:
May your new year be happy and prosperous.
-
As promised, I generated a 2.1.0 binary that is compatible with both 10.3 and 10.4. More details on the main page. :)