Recent fix_lib64 change breaks on CentOS6

[dstanek]

Merge request #335 seems to have broken virtualenv in my environment. I end up with this directory structure:

-bash-4.1$ ls -l venv/
total 4
drwxr-xr-x 3 dstanek agmail 4096 Sep 26 12:00 lib
lrwxrwxrwx 1 dstanek agmail    8 Sep 26 12:00 lib64 -> venv/lib

venv/lib doesn't exist. It should be ./venv/lib or better yet ./lib (which is what it used to be). I don't quite understand how ./lib causes #300. I always thought that the the . made the path relative to the link and not the current working directory.

It merge request also seems to fix #334 which appears to be an issue creating a virtualenv from within a virtualenv. Is that supported and/or wise?

[carljm]

#334 is not about creating a virtualenv from within a virtualenv, it's about re-running virtualenv on top of an existing virtualenv, which is supported.

And I'm not sure about #330 either, I didn't have access to a setup to reproduce it but I took the word of the reporter.

Presuming the report was accurate and the problem was caused by the use of a literal '.' in the symlink, it should be fixable by creating an even simpler same-directory symlink whose content is just "lib" (not "./lib" or "/full/path/to/venv/lib"). This is also better in case people are using --relocatable. I'm about to push that solution, please let me know if it solves your problem.