#include <hallo.h>
* M. Vefa Bicakci [Mon, Jul 05 2010, 09:21:25PM]:
> HTTP/1.1 206 Partial Response
>
> Content-Length: 64360088989315
>
> Content-Range: bytes
> 17496580076480779--5224466291009740840/-5314247457217970159
Yeah, that's the thing that apt-get should have displayed from the start
instead of the pointless "bad header" messages. The numbers are pure
mess, and as you have demonstrated below, this is most likely caused by
printf expressions not matching the width of the passed arguments.
> As you can see, the build by dpkg-buildpackage does not include the
> _FILE_OFFSET_BITS=64
> define statement.
Alright, good point. The package configuration sucks at some places and
this is one of them. I will add some code traps to report off_t size
mismatch and abort reliably.
> It looks like CXXFLAGS is now being defined by dpkg-buildflags, and because
> of this
> your custom CXXFLAGS were not being set.
If compiled using dpkg-buildpackage then yes, the value is overriden in
debian/rules. Mea culpa, I haven't done enough testing in 32bit
environment.
> So this causes file sizes to be messed up because of 32-bit wide integers,
> which
> explains why I kept getting file size related 503 errors.
>
> When I replaced the "?=" with "+=" in the Makefile, I was able to get a
> working binary
> via dpkg-buildpackage.
Right, that should do the job. I will release the fix ASAP.
Many thanks for the debugging work!
Regards,
Eduard.
--
Auf seine Freiheit verzichten heißt auf seine Menschenwürde,
Menschenrechte, selbst auf seine Pflichten verzichten.
-- Jean Jacques Rousseau
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
