A minor code-move, in anticipation of things yet to come.
Fix a bug discovered by inspection:

If we fail to allocate storage, try a smaller chunk, not a larger one.
Improve description
A restart in vcl_fetch{} needs to loose the objcore as well.

Fixes #1253
Also include the actual fix for 1253...
Make it possible to expect on the req.bodylen as well.
Fix a buglet which prevented req.body from being shown.
Revamp the req.body handling code.

There now is an undocumented facility for buffering the req.body,
but I'm not done testing it, and in particular the error handling
has not been exercised to any extent.
Ignore fd's larger than 65536 in varnishncsa

This makes varnishncsa behave the same way as varnishlog, and prevents
overly large memory allocations if it should see a bogus fd (shmlog
overrun?).

XXX: This will not fix varnishncsa for current trunk, as that is using
XIDs instead of FDs breaking some functionality in the tools. This
will be handled in the API rewrite.
Give the state engine a explanatory enum, rather than magic values
of 0, 1 and 2.
Release the storage of the cached req.body when the request is done.
VFP_update_length() was misnamed:  It is not a VFP function at all,
it is a VBO function which extends the busy object with data which
streaming clients can access.

Name it VBO_extend() instead and move it home to the rest of the
VBO functions.
Make the VFP_ methods take a "void *priv" rather than a busyobj,
to pave the way for sharing some code on client and backend side.
Rename httpconn to http1_proto, for increased clarity in a more
complex future world.
Move bodystatus into struct http_conn
Make sure to distribute req_body.h too
make autocrap(tm_phk) tools happy

Reduce warning noise from autoconf
Make automake happy
Pull in current ld-version-script.m4 which fixes the issue documented here:
https://lists.gnu.org/archive/html/bug-gnulib/2010-08/msg00198.html

From c24a91405479e7e5bd2633173cf5a24eabbd75fc Mon Sep 17 00:00:00 2001
From: Nils Goroll <nils.goroll@uplex.de>
Date: Wed, 9 Jan 2013 19:45:14 +0100
Subject: [PATCH] make autocrap(tm_phk) tools happy

Reduce warning noise from autoconf
Make automake happy
Pull in current ld-version-script.m4 which fixes the issue documented here:
https://lists.gnu.org/archive/html/bug-gnulib/2010-08/msg00198.html
proper dependencies for vmod automake

parallel builds (make -jX) failed sporadically for the first compilation
(before dependency tracking information was available) due to the race
with python building vcc_if.h

From 8e2751a28b7cb6331b386fbf6e1a7b1bdeafb4b7 Mon Sep 17 00:00:00 2001
From: Nils Goroll <nils.goroll@uplex.de>
Date: Wed, 9 Jan 2013 20:46:13 +0100
Subject: [PATCH] proper dependencies for vmod automake

parallel builds (make -jX) failed sporadically for the first compilation
(before dependency tracking information was available) due to the race
with python building vcc_if.h
Build vmods as shared objects only

It does not make any kind of sense to build a vmod as a static
library, so tell libtool to only build a shared one.
From @slink:

	tmo can become negative if timeout_idle gets changed on the fly
	or when the rtc jumps