I got around it temporarily by adding -DTIMES to the compile flags. Also I found I had to do the same -L hack in test/Makefile or the tests would fail. I then went back to 0.9.6c and got it to work with the patch from Pier Fumagalli. I'd still like to know how to do it without requiring manual edits though.
- Dave Dykstra On Tue, Jan 22, 2002 at 04:18:22PM -0600, Dave Dykstra wrote: > The OpenSSL snapshot from 2 days ago seems to be explicitly wanting to use > "ftime" because many source files have code of the form > > #if .... && !defined(OPENSSL_SYS_MACOSX) > # define TIMES > #endif > ... > #ifdef TIMES > ... > #else > ftime(...) > #endif > > but even though there's a man page for ftime() on my MacOSX system, which > says that ftime() is in libcompat, there's no libcompat. Did whoever put > in that OpenSSL code have a MacOSX system that does have ftime()? > > The snapshot has flags which appear to explitly not use any system copies > of old openssl header files for type darwin-ppc-cc, and I manually added > apps/Makefile (as I described below) to link with the static libraries, but > anyway this seems independent of any problem with the system installation > of OpenSSL. > > - Dave Dykstra > > > > On Fri, Jan 18, 2002 at 04:51:33PM -0600, Dave Dykstra wrote: > > Pier Fumagalli <[EMAIL PROTECTED]> wrote: > > > Still got some problems dealing with MacOS/X (Darwin 1.4), so I figured, what > > > the heck, better do it myself :) Two small problems (undrelated to the patch): > > > first apple bundles the OpenSSL libraries w/o includes and in a stripped-down > > > version, and Apple's LD is broken (doesn't correctly interpret the "-L" > > > library path search algorithm: meaning that libs in /usr/lib are checked > > > before the ones specifed in "-L", screwing up the whole thing because all > > > binaries don't want to compile). > > > > > > My hint - or solution :( is to remove the /usr/lib/libcrypto.* and > > > /usr/lib/libssl.* _BEFORE_ compiling OpenSSL.... > > > > > > I just tried compiling 0.9.6c also on Mac OSX and ran into the same problem. > > Removing something from /usr/lib is not a solution that works for me. I've > > found from another package that the -L algorithm is to search first through > > all the directories for a dynamic library and then to search through all > > the directories for a static library. So it should work if you're building > > a shared library, but I only want static libraries. I think all that's > > needed is to somehow replace $(LIBCRYPTO) and $(LIBSSL) in apps/Makefile > > with the contents of $(DLIBCRYPTO) and $(DLIBSSL) which refer directly to > > the "lib<name>.a" instead of using "-L -l<name>". It looks like the > > Makefile in that directory is not generated by a script though so I'm not > > sure how to do it in a way that will work with or without shared > > libraries. Any suggestions? > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
