[#2120] Initial support for Solaris.

Why?
------

Because we need to build and test Solaris packages of our software.


Solution?
-----------

Start with making python-package work on Solaris 10u11 x64.

Initial hurdles:

  * `/bin/sh` is the Bourne shell in Solaris, which is not even POSIX-compliant
  * `tr` was invoked with a non-portable expression
  * `uname -p` is not a reliable way to detect native arch on Solaris
  * GNU make is `gmake` and lives by default in `/usr/sfw/bin/`
  * added `/usr/css/bin` in front of the path in order to favour the BSD-flavoured `install`  over the system one. The path is needed for finding `ar` too.
  * added `Setup.local` file for OpenSSL libs and includes which on Solaris 10 live in `/usr/sfw/`
  * export `$ARCH` so that we are able to link to 64-bit libs when appropriate
  * added explicit CFLAGS and LDFLAGS to build 64-bit binaries on 64-bit Solaris
  * added `build_ext` step for linking pyOpenSSL to the default-included OpenSSL
  * patched `Setup.py` to add appropriate paths for SSL and Kerberos includes and libs
  * patched `Setup.py` to fix `libcrypt` build problem as per http://bugs.python.org/issue1471934
  * used external `libffi` in the same way as in AIX.

**Drive-by fixes**:

  * make sure $MAKE is exported to `src/python/chevahbs` in Linux too, otherwise the Linux builds fail with:
```
Installing...
install: missing destination file operand after `DESTDIR=/home/chevah/python-package/build/python2.7-sles11-x64'
Try `install --help' for more information.
```

How to check?
------------------

Please review the changes.
Build the package on Solaris 10.
Make sure builds for other OS'es don't break  (tested on AIX 5.3, Ubuntu 12.04 x86 and SLES11 SP1 x64). 


reviewers: @adiroiban