Problem Fixed

Sorry about that. Apparantly insead of renaming the libs from libcrypto.0.9.7 to 0.9.8, it seems like the scheme has changed to just simply be libcrypto.a, I was expecting to find *.0.9.7 and 0.9.8 libs in the same directory and just delete the old ones, but the name change had me fooled. also of note, the findssl.sh script didn't locate those, even though all of them were in the /usr/lib dir. So to summarize:
I Deleted the following from /usr/lib:
libcryto.0.9.7.dylib
libcrypto.0.9.dylib
libcrypto.dylib
libcrypto.a

And then copied the libcrypto.a from my newly installed openssl directory into /usr/lib

I didn't touch libssl.0.9.7.dylib, and make didnt complain, so whatever.

Did I get it right here? or what.

this is openssh-4.3p2 and openssl-0.9.8b on mac osx 10.4.6 (ppc)

Josh

Relevant Pages

  • Re: CL-UNIFICATION as a library (Re: Qi Seems Great)
    ... Scheme, but from seeing PLT Scheme and having in mind that there is a ... It's a living standard because different implementors of the many ... It's better because the whole IT world is built onto C/C++, ... Which libs are available to C++? ...
    (comp.lang.lisp)
  • Re: Ann: Sketchy LISP, Third Edition
    ... feature, but by removing the weaknesses and restrictions that make ... I don't think Scheme is well suited for this. ... It's not like Scheme didn't have libs, just that it makes it pretty ... procedures and macros defined in terms of core procedures. ...
    (comp.lang.scheme)
  • Re: Extol virtues of Lisp, but then use Python?
    ... The problem with Scheme is not a lack of libraries: there's plenty of awesome libraries out there, scattered around the personal pages of some true code warriors, implementation specific libs as well and the SRFIs. ... The main problem with Scheme is a lack of standard interfaces so that these libs could work out-of-the-box in any Scheme implementation. ... records and portable modules should have a nice benefic effect on the Scheme landscape in years to come. ...
    (comp.lang.scheme)