On Tue, Dec 12, 2000 at 04:38:59PM +0200, Dimitrios Souflis wrote:
> If the build process could at least be disassociated from Perl, it would be
> helpful to those with old systems without the latest Perl, or without any Perl
> at all. Perl is even more difficult to setup, and a *huge* download file.
The "latest Perl" should not be needed, though occasionally
incompatible constructs slip in (such as "for my $var (@foo)"
instead of "my $var; for $var (@foo)"). It has to be Perl 5.x,
though.
What is difficult about building Perl? "sh Configure -d -Dprefix=/opt/perl"
did it for me.
I agree that the build process should be self-contained, if possible;
and much of the guesswork in config/Configure and e_os.h would be
better left to an autoconf-generated configure script. However, for
OpenSSL *development*, Perl will be needed -- various source code files
are generated or changed by Perl, and it doesn't really make
sense to change this. If we don't want to rely on Perl being
available at compile time, we'll have to add some automatically
generated files.
(Should we port the Perl portions in test/Makefile.ssl to awk?)
--
Bodo M�ller <[EMAIL PROTECTED]>
PGP http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller/0x36d2c658.html
* TU Darmstadt, Theoretische Informatik, Alexanderstr. 10, D-64283 Darmstadt
* Tel. +49-6151-16-6628, Fax +49-6151-16-6036
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
