> On Jul 30, 2015, at 16:41, Ryan Senior <[email protected]> wrote: > > I think I have found a bug in the linkage of OSX standalone binaries. I run a > command like: > > csc -deploy nodes-script.scm > > I get a nodes-script directory with two files like I would expect: > > $ ls nodes-script/ > libchicken.dylib nodes-script > > But when I run otool -L on the nodes-script binary, it shows that it's linked > with the system libchicken, not the one included in the nodes-script > directory: > > $ otool -L nodes-script/nodes-script > nodes-script/nodes-script: > > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation > (compatibility version 150.0.0, current version 1153.18.0) > /usr/local/lib/libchicken.dylib (compatibility version 1.0.0, current > version 1.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 1213.0.0) > > Is this a bug? I went through the same process on a Debian VM and found the > binary was linked correctly (i.e. the nodes-script binary was linked to the > local libchicken). > > I have installed chicken via 'brew install chicken', with version info below: > > $ csc -version > (c) 2008-2014, The Chicken Team > (c) 2000-2007, Felix L. Winkelmann > Version 4.9.0.1 (stability/4.9.0) (rev 8b3189b) > macosx-unix-clang-x86-64 [ 64bit manyargs dload ptables ] > bootstrapped 2014-06-07
I've reproduced this in the same environment, but with manually compiled 4.10.0rc4 otool shows: /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1153.18.0) @executable_path/libchicken.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0) Looks like this was fixed already. — Regards, Oleg Art-System _______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
