Your message dated Mon, 22 Oct 2007 11:28:58 +0200
with message-id [EMAIL PROTECTED]
and subject line Warning clean on libqt3-headers 3.3.4-3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
---BeginMessage---
Package: libqt3-headers
Version: 3.3.4-3
Hello,
Here's a minor bug report(Warning clean) and an associated patch for
libqt3-headers 3.3.4-3.
I use libqt3-headers 3.3.4-3 as shown :
$dpkg -l | grep libqt
ii libqt2 2.3.1-22 Qt GUI Library (runtime version).
ii libqt3-dev 3.3.4-3Qt development files
ii libqt3-headers 3.3.4-3Qt3 header files
ii libqt3c102 3.3.4-3Qt GUI Library, Version 3
ii libqt3c102-mt 3.3.4-3Qt GUI Library (Threaded runtime version), V
ii libqtcups2 2.0-4 Qt interface library for CUPS
ii libqthreads-12 1.6.7-1QuickThreads library for Guile
ii libqttestrunne 1.10.2-3 Unit Testing Library for C++
While compiling with a higher warning level, I came on the following warning :
usr/include/qt3/qmemarray.h: In member function `QMemArraytype
QMemArraytype::duplicate(const type*, unsigned int) [with type = char]':
/usr/include/qt3/qcstring.h:252: instantiated from here
/usr/include/qt3/qmemarray.h:85: warning: cast from `const char*' to `char*'
discards qualifiers from pointer target type
A simple patch to this is to remove the cast in qmemarray.h as this :
85c85
{ return (QMemArraytype)QGArray::duplicate(a,n*sizeof(type)); }
---
{ return
(QMemArraytype)QGArray::duplicate((char*)a,n*sizeof(type)); }
Hope this helps.
Thanks for all your good work, have a nice day.
---End Message---
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
thanks for your report. This was fixed somewhere between 3.3.4-3 and
3.3.7-9 - as I don't know when exactly, I'm closing this bug without
specifying the version number where the bug was fixed.
Cheers,
Bernd
- --
Bernd Zeimetz
[EMAIL PROTECTED] http://bzed.de/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHHG1aBnqtBMk7/3kRCrGWAJ9v5iX4yKdvyvuCc0SHExwrcaJaJgCfd51G
ABHbFvwLGUa7KqQjux7tq4g=
=GqIv
-END PGP SIGNATURE-
---End Message---
