setenv() undeclared on Solaris

Rob Browning rlb@defaultvalue.org
Sat, 17 Nov 2001 18:35:48 -0600


Dave Peticolas <dave@krondo.com> writes:

> Yes, every release time we usually end up going around and removing
> all of the setenv calls that have crept in. putenv is used
> everywhere else so we might as well just standardize on that. With
> g_strdup_printf, it's not that big of a deal, anyway.

OK, though we need to fix your fix :>

putenv uses the pointer you hand it directly, so if you malloc that
pointer, you can't free it.  That's why I'd originally gone with
setenv (interface is cleaner)...

Took me a while to realize what was causing my "make check" failures
:>

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD