The MS-Windows runtime doesn't provide setenv. Use _putenv instead.
similar API, provided by any Windows DLL.
for MinGW to provide what isn't already provided by MSVCRT.DLL.
implicitly, so this becomes a compile time failure.
> lar API, provided by any Windows DLL.
Thanks for the explanation, Keith.
Please, do not send replies to the list to my e-mail.
naturally not visible from MSYS, whence I ran find.
some non-Windows implementation of putenv()? Linux' glibc perhaps?
> Does the Microsoft implementation copy the string passed?
> visible from MSYS, whence I ran find.
/mingw? Does find not traverse that mount point? (It does, for me).
"find -name", when running under MSYS.
>verse that mount point? (It does, for me).
>tion of putenv()? Linux' glibc perhaps?
>string, that would have been a practical necessity.
>>> Does the Microsoft implementation copy the string passed?
> getenv() returned a copy of the string as a safety measure.
in the environment has not been affected in any way.
> > > putenv(), would create a memory leak.
> > turned a copy of the string as a safety measure.
>> for the next mingwrt release).
Thanks, Anton. I added a proposed implementation patch to that ticket.