Re: bug in getenv/putenv on linuxppc/G4

"Jon A. Christopher" [off-list ref] writes:

I've just discovered a bug in either getenv (probably) or putenv (less
likely) on linuxppc on a G4, glibc-2.1.1-6c.

The attached test program demonstrates the bug.  Basically, using putenv
to add a variable to the environment whose name is only one letter long
and then using getenv to read it doesn't work.  

Variables with two or more letters are processed as normal.

I'm not sure if this is a glibc or a linuxppc problem, but I don't have
teh same problem on my intel RH 5.2 box, or any other unix I've ever heard
of.

It's a libc problem, reported on the libc-alpha list a few months
ago, and I think a patch was posted too.
It's fixed in glibc 2.1.2 in any case.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: mackan@stacken.kth.se

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/