Re: libcrypto linking problem in Leopard
Hi Dave, Able to change the path in the Mach O with the Install_name_tool, but while launching the app, it is checking the compatibility version and failing to launch. Here is the Otool output: /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.8, current version 47.2.0) Regards, Apparao Mulpuri Senior Systems Analyst, Mac Poker On 1/4/14 1:52 AM, St John, David R david.stj...@xerox.com wrote: On Jan 3, 2014, at 2:37 AM, Jean-Daniel Dupas devli...@shadowlab.org wrote: The simplest advice is don't use libcrypto. If you just need simple functionality, you may have a look at the CommonCrypto API which is partially available on 10.5 ( I think Digest and Cryptors where available at this time). If you need something more complex, you should use the Security framework, unfortunately the whole 10.5 API (CDSA) has been deprecated in favor of a cleaner but incompatible API. So you will have to write the code twice if you want to support 10.5 and be futur proof. Unfortunately, if you're using asymmetric encryption, you have to use the deprecated CDSA APIs, since (AFAIK) the newer APIs don't support it. Charles I had the same problem with libnetsnmp and solved it with a Run Script build phase. The linker puts the versioned dylib in the executable even though you include the non-versioned dylib, this switches the versioned back to non-versioned. install_name_tool -change ³versioned dylib² ³non-versioned dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH² In my case: install_name_tool -change /usr/lib/libnetsnmp.15.dylib /usr/lib/libnetsnmp.dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH Hope this helps, Dave ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/apparaom%40ivycomptech.c om This email sent to appar...@ivycomptech.com This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
There's lots of hurt trying to support that old. One thing that changed from 10.5 to 10.6 is some linking options so the dylibs are different. I tried to do the same thing you're trying for the sake of cross-platform compatibility, and I found it more resolvable to just factor out those calls that were in those libraries and call the OS X-explicit frameworks. If you want greater context, there are lots of other discussions on SO and elsewhere. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/ On Jan 6, 2014, at 5:41 AM, Appa Rao Mulpuri appar...@ivycomptech.com wrote: Hi Dave, Able to change the path in the Mach O with the Install_name_tool, but while launching the app, it is checking the compatibility version and failing to launch. Here is the Otool output: /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.8, current version 47.2.0) Regards, Apparao Mulpuri Senior Systems Analyst, Mac Poker On 1/4/14 1:52 AM, St John, David R david.stj...@xerox.com wrote: On Jan 3, 2014, at 2:37 AM, Jean-Daniel Dupas devli...@shadowlab.org wrote: The simplest advice is don't use libcrypto. If you just need simple functionality, you may have a look at the CommonCrypto API which is partially available on 10.5 ( I think Digest and Cryptors where available at this time). If you need something more complex, you should use the Security framework, unfortunately the whole 10.5 API (CDSA) has been deprecated in favor of a cleaner but incompatible API. So you will have to write the code twice if you want to support 10.5 and be futur proof. Unfortunately, if you're using asymmetric encryption, you have to use the deprecated CDSA APIs, since (AFAIK) the newer APIs don't support it. Charles I had the same problem with libnetsnmp and solved it with a Run Script build phase. The linker puts the versioned dylib in the executable even though you include the non-versioned dylib, this switches the versioned back to non-versioned. install_name_tool -change ³versioned dylib² ³non-versioned dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH² In my case: install_name_tool -change /usr/lib/libnetsnmp.15.dylib /usr/lib/libnetsnmp.dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH Hope this helps, Dave ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/apparaom%40ivycomptech.c om This email sent to appar...@ivycomptech.com This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/garywade%40desisoftsystems.com This email sent to garyw...@desisoftsystems.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
On Jan 2, 2014, at 11:15 PM, Appa Rao Mulpuri appar...@ivycomptech.com wrote: I am using Mac OS X 10.8 SDK for the development and deployment target set to Mac OS 10.5. I am using libcrypto dylib in my code base, application is working fine in all the OS, except in Leopard. Application is failing to launch in Leopard and giving the Library not loaded error. As Kyle says, you shouldn’t use those APIs. What functionality is it you need? You should look at using CommonCrypto and the Security framework instead. CommonCrypto handles most basic needs, and it’s in the system framework so you don’t need to link against anything extra. —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
Le 3 janv. 2014 à 08:15, Appa Rao Mulpuri appar...@ivycomptech.com a écrit : Hi List, I am using Mac OS X 10.8 SDK for the development and deployment target set to Mac OS 10.5. I am using libcrypto dylib in my code base, application is working fine in all the OS, except in Leopard. Application is failing to launch in Leopard and giving the Library not loaded error. Library not found: /usr/lib/libcrypto.0.9.8.dylib Reason: no suitable image found. I tried to build the application on mavericks with libcrypto.0.9.7.dylib by updating the libcrypto.dylib alias in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib, but no luck. Its giving me compile time errors saying symbols not found. I primarily wants to move to Mavericks for my regular development and take advantage of LLVM compiler for its greater speed (compared with GCC). http://stackoverflow.com/questions/2616738/linking-to-libcrypto-for-leopard gone though this url. Solution is available if you are using the 10.6 SDK for development. To make it work with 10.6 SDK + Xcode 5, copied 10.6 and 10.7 sdks into /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/, but unfortunately Xcode 5 is not displaying them in the Build settings window. Is there any way to get rid of the libCrypto linking issue? Regards, The simplest advice is don't use libcrypto. If you just need simple functionality, you may have a look at the CommonCrypto API which is partially available on 10.5 ( I think Digest and Cryptors where available at this time). If you need something more complex, you should use the Security framework, unfortunately the whole 10.5 API (CDSA) has been deprecated in favor of a cleaner but incompatible API. So you will have to write the code twice if you want to support 10.5 and be futur proof. -- Jean-Daniel ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
On Jan 3, 2014, at 2:37 AM, Jean-Daniel Dupas devli...@shadowlab.org wrote: The simplest advice is don't use libcrypto. If you just need simple functionality, you may have a look at the CommonCrypto API which is partially available on 10.5 ( I think Digest and Cryptors where available at this time). If you need something more complex, you should use the Security framework, unfortunately the whole 10.5 API (CDSA) has been deprecated in favor of a cleaner but incompatible API. So you will have to write the code twice if you want to support 10.5 and be futur proof. Unfortunately, if you're using asymmetric encryption, you have to use the deprecated CDSA APIs, since (AFAIK) the newer APIs don't support it. Charles ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
On Jan 3, 2014, at 2:37 AM, Jean-Daniel Dupas devli...@shadowlab.org wrote: The simplest advice is don't use libcrypto. If you just need simple functionality, you may have a look at the CommonCrypto API which is partially available on 10.5 ( I think Digest and Cryptors where available at this time). If you need something more complex, you should use the Security framework, unfortunately the whole 10.5 API (CDSA) has been deprecated in favor of a cleaner but incompatible API. So you will have to write the code twice if you want to support 10.5 and be futur proof. Unfortunately, if you're using asymmetric encryption, you have to use the deprecated CDSA APIs, since (AFAIK) the newer APIs don't support it. Charles I had the same problem with libnetsnmp and solved it with a Run Script build phase. The linker puts the versioned dylib in the executable even though you include the non-versioned dylib, this switches the versioned back to non-versioned. install_name_tool -change ³versioned dylib² ³non-versioned dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH² In my case: install_name_tool -change /usr/lib/libnetsnmp.15.dylib /usr/lib/libnetsnmp.dylib $TARGET_BUILD_DIR/$EXECUTABLE_PATH Hope this helps, Dave ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
libcrypto linking problem in Leopard
Hi List, I am using Mac OS X 10.8 SDK for the development and deployment target set to Mac OS 10.5. I am using libcrypto dylib in my code base, application is working fine in all the OS, except in Leopard. Application is failing to launch in Leopard and giving the Library not loaded error. Library not found: /usr/lib/libcrypto.0.9.8.dylib Reason: no suitable image found. I tried to build the application on mavericks with libcrypto.0.9.7.dylib by updating the libcrypto.dylib alias in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/usr/lib, but no luck. Its giving me compile time errors saying symbols not found. I primarily wants to move to Mavericks for my regular development and take advantage of LLVM compiler for its greater speed (compared with GCC). http://stackoverflow.com/questions/2616738/linking-to-libcrypto-for-leopard gone though this url. Solution is available if you are using the 10.6 SDK for development. To make it work with 10.6 SDK + Xcode 5, copied 10.6 and 10.7 sdks into /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/, but unfortunately Xcode 5 is not displaying them in the Build settings window. Is there any way to get rid of the libCrypto linking issue? Regards, Apparao Mulpuri Senior Systems Analyst, Mac Poker IVY Comptech Private Limited 6th Floor, Block B, Divyasree Omega, Kondapur, Hyderabad-500081. Mobile + 91 (0) 988 500 4790 DD + 91 (0) 40 4472 1000 ext: 4391 [Description: cid:D3A34606-CDE4-42D4-8A76-036EAFC49156@ivycomptech.partygaming.local] This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system. Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk. inline: AFFD875C-3115-48FA-BD66-A7D2DE95B85B[6].png___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: libcrypto linking problem in Leopard
On Thu, Jan 2, 2014, at 11:15 PM, Appa Rao Mulpuri wrote: Hi List, I am using Mac OS X 10.8 SDK for the development and deployment target set to Mac OS 10.5. I am using libcrypto dylib in my code base, Do not link directly against libcrypto (nor libssl). Its API is not stable between point releases, and new versions of OS X need to adopt new versions of libcrypto to incorporate security fixes. The stable library for performing cryptography is Security.framework. --Kyle Sluder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
