diff options
| author | Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 <daxim@cpan.org> | 2010-07-21 10:53:50 +0200 |
|---|---|---|
| committer | Florian Ragwitz <rafl@debian.org> | 2010-07-26 12:47:25 +0200 |
| commit | 33bb4a44218ade1a7fe78a286569fafa4ab02b7d (patch) | |
| tree | 7bb98a251498c8acf56902d41b4d08a88b9b9dfe | |
| parent | 278372729622ff1b3dfc1ecbf1efe8abb7f5b3fa (diff) | |
| download | perl-33bb4a44218ade1a7fe78a286569fafa4ab02b7d.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 |