On Sun, 6 Jan 2002, Pier Fumagalli wrote:
> My hint - or solution :( is to remove the /usr/lib/libcrypto.* and
> /usr/lib/libssl.* _BEFORE_ compiling OpenSSL
Removing libssl.* and libcrypt.* is a BAD idea - you'll break some
important stuff that's linked against them. E.g. Mail's Message
Probably because you're not using an ebcdic computer and ebcdic.o has no
symbols. You might be comforted by the line that precedes it:
"You may get an error following this line. Please ignore."
- sq
On Thu, 3 Jan 2002, Jay States wrote:
> why does /usr/bin/ranlib: file: ../../libcrypto.a(
thing? IIRC, you have to do some funky make invocations to
get this (SHLIB_EXT=.dyld &etc).
I'm not exactly sure what you mean by "partial configure", though.
Steve
------ Forwarded message --
Date: Thu, 3 Jan 2002 12:20:07 -0500 (EST)
From: Steve Quirk <[EMAIL PR
ld is trying to link against the lib that Apple ships. Before building
openssl (which will replace Apple's libs), you need to move/rename/unlink
/usr/lib/libcrypto.dylib and /usr/lib/libssl.dylib. Then you *might* be
able to build them.
Now, there's another issue from another email on the list
Has anyone done any work on the asm for the PPC platform? I'm using 0.9.6a
on Mac OSX.
gprof shows that most of my time is spent in the bn routines that are
normally asm (on other platforms):
% cumulative self self total
time seconds secondscalls ms/call ms/call
You're inadvertantly linking against the openssl 0.9.5 libraries that
Apple ships. Before typing 'make', remove the libraries
/usr/lib/libcrypto.dylib and /usr/lib/libssl.dylib and you should be on
the the next problem.
Steve
You need to remove the librari
On Thu, 12 Apr 2001, Ian Bishop wrot
The currently shipping OS X (public beta) comes with 0.9.5a installed.
One can make the assumption that Apple plans on taking care of
compatibility/support going forward.
I haven't tried it, but installing 0.9.6 should be straightforward.
('configure && make')
Steve
On Sat, 21 Oct 2000, Richa
