Hi, The problem is fixed with your patch. Thank you!
Regards, Cédric Marie. >________________________________ > De : Andy Polyakov via RT <[email protected]> >À : [email protected] >Cc : [email protected] >Envoyé le : Jeudi 19 avril 2012 8h48 >Objet : Re: [openssl.org #2793] bug report : SCRIPTS environment variable >overrides makefile variable > >Hi, > >> Installation of openssl-1.0.0e fails if SCRIPTS environment variable is >> defined (export SCRIPTS=/home/xxx/scripts for example). >> >> making install in apps... >> installing openssl >> installing /home/xxx/scripts >> >> In apps/Makefile, SCRIPTS is defined ("SCRIPTS=CA.sh CA.pl tsget"), but >> it seems that the makefile is called with -e option ("$(MAKE) -e"), >> which means that environment variables must override makefile local >> definitions. > >Verify http://cvs.openssl.org/chngview?cn=22430. > >> Why is it necessary to call "$(MAKE) -e"? > >It was the only way to get both GNU and SysV make flavors work consistently. > >> It is a little bit risky to use such an option. SCRIPTS variable is a >> common name, and people may define it in their shell rc file. > >Yes, it poses risk, but there is a way to handle it, CLEARENV. That's >what patch does, modifies CLEARENV. > > > > >
Hi,
The problem is fixed with your patch. Thank you!
Regards,
C?dric Marie.
De : Andy Polyakov via RT <[email protected]>
? : [email protected]
Cc : [email protected]
Envoy? le : Jeudi 19 avril 2012 8h48
Objet : Re: [openssl.org #2793] bug report : SCRIPTS environment variable overrides makefile variable
Hi,
> Installation of openssl-1.0.0e fails if SCRIPTS environment variable is
> defined (export SCRIPTS=/home/xxx/scripts for example).
>
> making install in apps...
> installing openssl
> installing /home/xxx/scripts
>
> In apps/Makefile, SCRIPTS is defined ("SCRIPTS=CA.sh CA.pl tsget"), but
> it seems that the makefile is called with -e option ("$(MAKE) -e"),
> which means that environment variables must override makefile local
> definitions.
Verify http://cvs.openssl.org/chngview?cn=22430.
> Why is it necessary to call "$(MAKE) -e"?
It was the only way to get both GNU and SysV make flavors work consistently.
> It is a little bit risky to use such an option. SCRIPTS variable is a
> common name, and people may define it in their shell rc file.
Yes, it poses risk, but there is a way to handle it, CLEARENV. That's
what patch does, modifies CLEARENV.
