python32: inconsistent naming of libraries

[jasper@…]

Build scripts use python3.2-config to determine the libraries to link against. When doing python3.2-config --libs, the script returns a reference to -lpython3.2m which does not exist in the macports build of Python 3.2.

A solution would be to add a symbolic link for both the static and the dynamic library in order to cover both the legacy naming scheme (without the abiflag 'm') and the config3.2-python provided one.