Re: Bug#178525: looking for help building xdelta2 with g++ 3.3
On Thu, Jun 12, 2003 at 12:48:59AM +0200, Yann Dirson wrote:
> On Wed, Jun 11, 2003 at 11:21:35PM +0100, Philip Martin wrote:
> > os << std::setbase(16) << 132;
>
> Ah OK, I was also pointed to:
>
> os << std::setw(4) << std::hex << 132 << std::dec;
>
> Unfortunately, that will make the code much longer and much less
> readable. And there are also uses of ostrstream::vform(), to apply a
> format passed by argument to other arguments. I guess I'll have to
> fallback to vsnprintf() for this, with either the inherent problems of
> string-length management.
>
> And I thought C++ was a high-level language :(
How's progress on this bug? Do you need any more help?
At the moment, the version of xdelta2 in testing depends on libdb3++,
which has been removed in unstable in favour of libdb3++c102. As a
result, db3 is blocked from progressing into testing until a fixed
xdelta2 is available; this isn't solely responsible for holding up too
much else just yet, but it probably will be soon (libsigc++ and
jack-audio-connection-kit being the main things I've noticed so far).
If it's going to be a while until a fixed xdelta2 is available, then
perhaps we should temporarily drop xdelta2 from testing and let it back
in once it's fixed. Anthony, what do you think?
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: