Hi

Thanks a lot.

I'll look at this.

Regards,

// Ola

On Thu, Mar 02, 2006 at 02:46:45PM +0100, Daniel Schepler wrote:
> Le Samedi 25 Février 2006 17:33, Ola Lundqvist a écrit :
> > tags 354206 + unreproducible moreinfo
> > severity 354206 important
> > thanks
> >
> > Hello
> >
> > On Fri, Feb 24, 2006 at 10:43:50AM +0100, Daniel Schepler wrote:
> > > Package: steghide
> > > Version: 0.5.1-7
> > > Severity: serious
> >
> > I can not reproduce this problem (on latest etch). For what architecture do
> > you build it and with what versions of relevant software?
> >
> > As I could not reproduce the problem I lowered the severity to important
> > until you have given me more information so it is possible to reproduce.
> >
> > I compiler should not have a problem to convert between
> > 'uint8_t*' and 'char*' unless there is a serious problem with them.
> 
> I just tried again with a freshly updated pbuilder (unstable) i386 chroot and 
> got the same error again.  The version of g++-4.0 there is 4.0.2-9, and the 
> version of libmhash-dev is 0.9.4a-1.
> 
> It looks like it's complaining about assigning the result of 
> mhash_get_hash_name, which is of type mutils_word8*, to a char* variable, 
> which would involve an implicit conversion.  So it's validly complaining 
> about invalid C++ code.  Of course, if mhash_get_hash_name is actually 
> supposed to return a user-readable string, it's probably a bug in mhash to 
> return the result as a uint8_t* instead of a char*.
> -- 
> Daniel Schepler
> 
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to