libgcc-static: do not dynamically link with libgcc.
test-python26-compat: make test python 2.6 compatible.
Fix a bug with concurrent invocation of session triggers.

A session trigger would always use the same coroutine, for both connect and
disconnect, as well as for multiple sessions.

If a trigger runs insert() or update(), anything that yields the current
coro, the coro stack would get corrupted for the next parallel invocation.

Use an own coroutine for each invocation of a session trigger.
Merge branch 'stable'
Fix broken (crashing) command line client on Ubuntu Precise

libreadline already goes with libhistory compiled in,
no reason to add it to the dynamically linked library
list.
Apparently, explicitly listing libhistory leads to
the dl loader pre-loading it instead of the compiled-in
version, which, in turn, leads to a crash on the first
history search in the command line client.

The fix is to remove cmake dependency on libhistory
as well as on libncurses, which we don't need either
(always require libtermcap).
Merge branch 'stable'
Update the user guide.
Merge branch 'stable' of github.com:mailru/tarantool into stable
Merge branch 'test-python26-compat'
Merge branch 'warning-fix'
Fix a bug with session id in on_disconnect() trigger.

https://bugs.launchpad.net/tarantool/+bug/1160789

When multiple sessions get disconnected at the same
time, the same fiber is running all disconnect triggers.
This fiber's sid was  not changed between trigger invocations,
and on_disconnect() triggrer of the next disconnected
session would see not its own session id in box.session.id(),
but the previous session's session id.

The fix is to correctly set box.session.id() before handling
any iproto request.
In on_connect() request, sid is 0, but soon it is
reset in session_create().

No test case since the bug requires that there is a full
libev queue, so that multiple on_disconnect() triggers
fire in the same loop.
Merge branch 'stable'
Bug1160869: incorrect fiber call order.
(https://bugs.launchpad.net/tarantool/+bug/1160869)

Lua socket object creates coio object that bind to a current
fiber, after yield it will resume it in a different fiber
context after a complete io operation.

Fix this situation by updating current coio fiber in most
lua socket operations.
bug1160877: loopback addresses are not ignored when the AI_ADDRCONFIG
flag is set.
(https://bugs.launchpad.net/tarantool/+bug/1160877)

getaddrinfo("::1") may fail if machine has no public ipv6 addresses due
to AI_ADDRCONFIG behaviour.
Minor edit of a comment.
coio-fiber-detach: move coio fiber update from lua socket to coio itself.
Merge branch 'master' into coio-fiber-detach
coio-fiber-detach: review fixes.
Merge branch 'master' of github.com:mailru/tarantool into remote
delay until box.socket will be fixed