New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clarify how to enable -DPERL_USE_SAFE_PUTENV #10499
Labels
Comments
From @daximCreated by @daximLook at the config_args below. Can you see the mistake I made when I built Perl Info
|
From @daxim0001-clarify-how-to-enable-DPERL_USE_SAFE_PUTENV.patchFrom dff6190919db2ceb0819c035539d2e19318e2d30 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lars=20D=C9=AA=E1=B4=87=E1=B4=84=E1=B4=8B=E1=B4=8F=E1=B4=A1=20=E8=BF=AA=E6=8B=89=E6=96=AF?= <daxim@cpan.org>
Date: Wed, 21 Jul 2010 10:53:50 +0200
Subject: [PATCH] clarify how to enable -DPERL_USE_SAFE_PUTENV
---
INSTALL | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/INSTALL b/INSTALL
index 1e5ef68..5346337 100644
--- a/INSTALL
+++ b/INSTALL
@@ -495,9 +495,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
--
1.7.1
|
From @raflThanks, applied. |
From [Unknown Contact. See original ticket]Thanks, applied. |
@rafl - Status changed from 'new' to 'resolved' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Migrated from rt.perl.org#76618 (status was 'resolved')
Searchable as RT76618$
The text was updated successfully, but these errors were encountered: