Date: Fri, 08 Dec 2000 14:14:03 -0800
From: Michael Sierchio <[EMAIL PROTECTED]>
Richard Levitte - VMS Whacker wrote:
> Oh well, I've been thinking of doing a Makefile haul-over for some
> time, perhaps that time is now (or at least in the near future)...
automake? autoconf? Pleez?
Somethine like 2 years ago, probably more, I offered a set of diffs
from SSLeay 0.8.1 which make it use automake and autoconf. I was
using that to embed SSLeay in an open-source application that shipped
and ran on half a dozen platforms. It worked great.
This offer was roundly ignored, in part because a US contribution to
SSLeay would run it afoul of US export law (not an issue any more),
and because automake/autoconf didn't fit well into Windoze platforms
(I think---this is from memory); I don't know if this is true, or
whether OpenSSL requires other things (CygWin?) which might make this
less of an issue. (I have -not- been tracking Win versions of OpenSSL.)
I would be overjoyed to have OpenSSL use autoconf/automake, because
its lack of use has significantly interfered with any future plans to
migrate my application from SSLeay to OpenSSL. (The entire rest of my
application---hundreds of thoussands of lines of code---uses
autoconf/automake.) My alternates are either to continue to play
catchup & merge to keep -my- version of OpenSSL using autoconf, or to
just freeze on SSLeay 0.8.1 and abandon further updates. For the
moment, I've unfortunately had to do the latter, due to lack of
resources to constantly play catchup on this---I have to make progress
on the -rest- of the system, too.
In addition, OpenSSL's build process relies on having Perl installed
(right?), which also complicates life for my users who would like to
recompile the app, because it means that they must install the -right-
version of Perl in order to even -start- recompiling! I certainly
remember traffic of a few months ago demonstrating that subtly "wrong"
versions of Perl failed in strange ways.
I would be overjoyed to send my old diffs (with a CC to the BXA or
to the crypto repository, to ensure that US export laws have been
complied with) if I thought that they would help jump-start use of
automake and autoconf in OpenSSL. I'm sure that a ONE-SHOT
integration of them with OpenSSL really would -not- be a huge
undertaking. I'd even help! And I could probably get additional
help. But having to do myself, -against the moving target of an
OpenSSL that isn't using it-, is too much work for me to keep up
with. There's a big difference in workfactor here.
If I see mail from anyone saying that they'd like the diffs, I will
post them. I would rather post just a URL to the diffs, but I'm not
sure that this complies with US export regs (especially since I'd
rather not leave the diffs up "forever"); I would welcome enlightenment
on this issue, since I'd much rather put 100 bytes of URL than many
hundreds of K of diffs into everyone's mailbox...
Thanks!
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
