Resolution of the library-path mess

[Hal Murray]

>> Warnings are easily lost in the noise.  So either create the
>> directory or treat it as an error and bail.

> There are two issues with just "creating the directory":
> 1) There's no guarantee that Python will actually use it.
> 2) Creating the directory requires root, and it would be
> undesirable to require that 'configure' run as root.

The actual create can be deferred until the install.

I don't understand the comment about "actually use it"?  Is that any 
different from the case where the directory did exist?

-- 
These are my opinions.  I hate spam.