Turns out that test_disable_namespace_lock wasn't actually being run (and it's broken)
Fix setenv() invocation

setenv takes a char* as the second argument (ie. a pointer), one that's
really meant to be not-null. A bare zero (int) is not valid as it would
be NULL.
We meant to disable locking there, right?

Not sure what the intent was here. We intended to say "yes disable
locking", but setenv'd the value to 0 (ie. don't disable locking).

Nevermind that we're not handling this properly as a string yet, I think
"1" was intended.
Fix handling of DISABLE_NAMESPACE_LOCK

DISABLE_NAMESPACE_LOCK was being read as an int, which makes no sense
when it's actually a char*. If you read a pointer address as a boolean
int, you're gonna have a bad time.
Merge pull request #28 from anchor/barney-fix-gcc-warnings-locking

Fix namespace locking logic