diff options
| author | Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <daxim@cpan.org> | 2010-07-21 10:53:50 +0200 |
|---|---|---|
| committer | Craig A. Berry <craigberry@mac.com> | 2010-08-22 09:59:42 -0500 |
| commit | 4159e58391a03f23a86a00e978cc2bf3a3219996 (patch) | |
| tree | f3348e1053ad5761837fd9d48dade9305a5552e4 | |
| parent | c9967a7f1535df046a0e67efb3ce8f456a7ce269 (diff) | |
| download | perl-4159e58391a03f23a86a00e978cc2bf3a3219996.tar.gz | |
clarify how to enable -DPERL_USE_SAFE_PUTENV
| -rw-r--r-- | INSTALL | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -500,9 +500,10 @@ to avoid these leaks. The default is now to perform direct manipulation whenever perl is running as a stand alone interpreter, and to call the safe but potentially leaky C<putenv()> function when the perl interpreter is embedded in another application. You can force perl to always use C<putenv()> -by compiling with -DPERL_USE_SAFE_PUTENV. You can force an embedded perl to -use direct manipulation by setting C<PL_use_safe_putenv = 0;> after the -C<perl_construct()> call. +by compiling with C<-Accflags="-DPERL_USE_SAFE_PUTENV">, see section +L</"Altering Configure variables for C compiler switches etc.">. +You can force an embedded perl to use direct manipulation by setting +C<PL_use_safe_putenv = 0;> after the C<perl_construct()> call. =head2 Installation Directories |