Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Version Linking Issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Version Linking Issues

Subject: Re: Version Linking Issues
From: Matt DeFoor <email@hidden>
Date: Wed, 28 Sep 2005 12:19:43 -0400

Mark Thomas wrote:

Thanks for the link, I tried putting in my other Linker flags "-lcrypto
-lssl", which caused an output of
Ld /Volumes/Dev/BTDev/WebTest/build/Install.app/Contents/Resources/220DLL.dylib cd /Volumes/Dev/BTDev/220DLL /usr/bin/g++-3.3 -o /Volumes/Dev/BTDev/WebTest/build/Install.app/Contents/Resources/220DLL.dylib -L/Volumes/Dev/BTDev/WebTest/build/Install.app/Contents/Resources -F/Volumes/Dev/BTDev/WebTest/build/Install.app/Contents/Resources -filelist /Volumes/Dev/BTDev/220DLL/build/220DLL.build/220DLL.build/Objects-normal/220 DLL.LinkFileList -framework Carbon -framework CoreServices -arch ppc -prebind -Wl,-single_module -dynamiclib -compatibility_version 1 -current_version 1 -install_name /usr/local/lib/220DLL.dylib -lcrypto -lssl So then I used otool on a 10.3.8 system $otool -L 220DLL.dylib 220DLL.dylib: /usr/local/lib/220DLL.dylib (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 16.0.0) /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7) /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 71.1.1) Then on 10.2.8 I did, to make sure the right library was pulled in, but wasn't

[Mark-Thomass-Computer:/Volumes/Mac Pen Drive] coderus% otool -L 220DLL.dylib 220DLL.dylib: /usr/local/lib/220DLL.dylib (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 128.0.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 16.0.0) /usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7) /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
But there is only libssl.0.9.dylib and libcrypto.0.9.dylib exist in
/usr/lib, but if the dylib stored the link name this would work correctly.
Anybody know of how to get this to work correctly, or did I miss something
here ?. (I saw Daniel comment, but is that the only solution as I would
always plan to use the latest version.)


I've experienced the same problem. I've followed everyone's suggestion
to use -l<libary> but it still links against the wrong version. I've had
to abandon XCode 2.1 for builds for 10.2.x. I use XCode 1.2 on 10.3.9 to
build and link properly. So much for one build system...

--
/* Matt DeFoor */

Listening to the sound of silence

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >Re: Version Linking Issues (From: Mark Thomas <email@hidden>)




Prev by Date:
viewing globals?

Next by Date:
Re: EXC_BAD_ACCESS when running from different drive

Previous by thread:
Re: Version Linking Issues

Next by thread:
Re: Version Linking Issues

Index(es):

Date
Thread