On Wed, Jun 05, 2002 at 03:15:18PM +0200, Lutz Jaenicke wrote:
> On Wed, Jun 05, 2002 at 02:47:24PM +0200, Bodo Moeller wrote:
> > On Wed, Jun 05, 2002 at 09:01:53AM +0200, [EMAIL PROTECTED] wrote:
> >
> > > Log:
> > > The correct PERL interpreter is passed via commandline.
> >
> > > RCS file: /e/openssl/cvs/openssl/apps/Makefile.ssl,v
> > > retrieving revision 1.100.2.2
> > > retrieving revision 1.100.2.3
> > > diff -u -r1.100.2.2 -r1.100.2.3
> > > --- Makefile.ssl 2002/04/06 19:14:48 1.100.2.2
> > > +++ Makefile.ssl 2002/06/05 07:01:13 1.100.2.3
> > > @@ -14,7 +14,6 @@
> > > MAKEDEPPROG= makedepend
> > > MAKEDEPEND= $(TOP)/util/domd $(TOP) -MD $(MAKEDEPPROG)
> > > MAKEFILE= Makefile.ssl
> > > -PERL= perl
> > > RM= rm -f
> > > # KRB5 stuff
> > > KRB5_INCLUDES=
> >
> > Is there a particular reason for deleting these definitions? The
> > value passed on the command line will override the value found in the
> > Makefile anyway, so there should be no harm in keeping the
> > PERL=... line.
>
> Yes, that's what I also read in the manual page. The more problems I have
> to explain why it didn't work as expected... (HP-UX 10.20)
>
> > The reason for providing a PERL definition in the Makefile, even
> > though it will be ignored under usual circumstances, is that otherwise
> > very strange things might happen if make is run without a PERL
> > definition on the command line. We could use 'PERL=false' to ensure
> > that make will fail in a predictable way in such cases.
>
> Sounds reasonable. Probably I should take another look to find out, why
> it didn't work out in the first place, because it would break things again
> otherwise...
Explanation found:
When calling "make" in the openssl/ directory, everything is fine (with
or without the PERL entry in apps/Makefile.ssl).
However: when calling "make test", the main Makefile will enter the test/
subdirectory, there calling "make" will all settings (including PERL)
passed on the command line. test/Makefile.ssl will call "make" for the
"../apps" directory without passing the settings. Therefore the PERL
setting in apps/Makefile will take precedence.
The correct solution would therefore be, to pass all options back from
withing test/Makefile (which would call crypto/ and ssl/ builds in
case libcrypto and libssl are not yet build).
Comments?
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
http://www.aet.TU-Cottbus.DE/personen/jaenicke/
BTU Cottbus, Allgemeine Elektrotechnik
Universitaetsplatz 3-4, D-03044 Cottbus
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
