Bugfix: configure: Look in libx32 subdirectory for boost libraries
Add CLIENT_VERSION_REVISION to mac osx info plist
[Qt] Optionally add third party links to transaction context menu
Correct indentation
use standard __func__ instead of __PRETTY_FUNCTION__
gitian: build against Qt 4.6

Should make it possible to run the resulting GUI executable on
Linux distributions that use Qt 4.6, such as Debian Wheezy and Tails.

Builds a mini-SDK for building against Qt 4.6. This includes the headers
as well as host utilities such as `lrelease`, `qrc` and `moc`.

This speeds up the gitian build a bit - libqt4-dev pulled in a lot of packages,
and is no longer needed as this provides a replacement of our own.

Note: This does not replace the Qt build with at static library. After this
commit we still build dynamically against the system Qt library. The only
difference is that compatibility with an older version is maintained. This
loses minor GUI functionality (such as setPlaceholderText) but still
allows integration into the window management of the host OS, unlike
when statically linking.
gitian: don't export any symbols from executable

This avoids conflicts between the libraries statically linked into bitcoin and any
libraries we may link dynamically (such as Qt and OpenSSL, see issue #4094).
It also avoids start-up overhead to not export any unnecessary symbols.
To do this, build a linker script that marks all symbols as local.
devtools: have symbol check script check for exported symbols

After last commit, our executables should export no symbols anymore.  To
make sure that this stays the case, verify this in the symbol checker
script.
Merge pull request #4111

1cc7f54 use standard __func__ instead of __PRETTY_FUNCTION__ (Philip Kaufmann)
Merge pull request #4109

6b29ccc Correct indentation (R E Broadley)
Merge pull request #4092

40c5b93 [Qt] Optionally add third party links to transaction context menu (Cozz Lovan)
Merge pull request #4088

8abfb99 Add CLIENT_VERSION_REVISION to mac osx info plist (Michael Ford)
Log BerkeleyDB version at startup

Prints the actual version of BerkeleyDB that is linked against, if
wallet support is enabled.

Useful for troubleshooting.

For example:

    2014-05-01 07:44:02 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)

    2014-05-01 07:54:25 Using BerkeleyDB version Berkeley DB 5.1.29: (October 25, 20 11)
Update build instructions for Berkeley DB

- People were having problems with the .so when installing in
  alternative locations.
  Like gitian, build a static library with -fPIC that can
  be embedded into the executables.

- Add some missing steps

- Add reminder that BerkeleyDB is only needed when wallet support is
  enabled
qt: add transifex configuration file

This is a project-wide configuration file and should be the same for
everyone.
Also remove mention of creating it yourself from the translation process.
devtools: add a script to fetch and postprocess translations

Run this script from the root of the repository to update all translations from transifex.
It will do the following automatically:

- create a transifex configuration file
- fetch all translations
- post-process them into valid and committable format
Full translation update

Last update (48be9ce) missed quite a lot, for some reason.

This is also the first update done with the new script
`contrib/devtools/update-translations.py`
Remove build-time no-IPv6 setting

The year is 2014. All supported operating systems have IPv6 support,
most certainly at build time (this doesn't mean that IPv6 is configured,
of course).

If noone is exercising the functionality to disable it, that means it
doesn't get tested, and IMO it's better to get rid of it.

(it's also not used consistently in RPC/boost and Net code...)
Removed LevelDB changes

Syntax Highlighting
Wording

Cleaned up wording and spacing for readability.