win32: always use safe API calls to manipulate environment

It turns out that with the new toolchain safe API calls work on all
all platforms.  Even the original code from commit fa147bd7e works
on Windows XP when built with the new tools.

- Remove the unsafe environment manipulation via the environ array
- Microsoft's putenv takes a copy of its argument so the string
  can be freed
- Rewrite some routines and add more error checking

1 files changed, 0 insertions, 10 deletions

diff --git a/Config.in b/Config.in
index ba7ba1026..dc3a6e09a 100644
--- a/Config.in
+++ b/Config.in
@@ -134,16 +134,6 @@ config GLOBBING
           the BusyBox binary to handle wildcard expansion using the C runtime
           set this to 'Y'.
 
-config SAFE_ENV
-        bool "Manipulate the environment through safe API calls"
-        default n
-        depends on PLATFORM_MINGW32
-        help
-          Enable this option to use safe API calls when clearing environment
-          variables.  This is necessary if BusyBox is to run on ReactOS or
-          64-bit Windows.  The default is 'N', which must be used if BusyBox
-          is to run on Windows XP.
-
 config PAM
         bool "Support PAM (Pluggable Authentication Modules)"
         default n