On 5/2/07, David Hyatt <[EMAIL PROTECTED]> wrote:
This seems like a pretty sad technical limitation of Purify.
Yes. I thought about this problem for a while, and the best
solution I came up with requires changes to compilers.
Using my example and pseudocode:
Suppose bit field x is the 0th b
This seems like a pretty sad technical limitation of Purify.
On May 2, 2007, at 5:31 PM, Anyang Ren wrote:
There are so many UMRs that I am forced to ignroe all UMRs.
This is bad. I am wondering if you'd consider not using bit fields
so that these UMRs can be eliminated. You can either just m
Hi,
I have gperf version 3.0.1-2 installed. I installed all the
packages specified in webkit.org documentation, but since I use Ubuntu 6.06,
the version of the packages is not always the latest. Do you think this is
the problem?
thanks,
On 5/2/07, Sebastien Le Faou <[EMAIL PROTECTED]> wrote:
H
I'm Purifying WebKit on Windows. I'm getting tons of UMR (uninitialized
memory read) warnings. Most of these seem to be in constructors of
classes that contain bit fields. These UMRs are benign but it is strictly
speaking correct for Purify to report them. So my question is: would
you trade off t
Hi,
I don't know if it's that but did you install gperf?
It could be that.
Have a good night.
Seb
ya ah wrote:
I am trying to build the QT port of WebKit on my Ubuntu 6.06 machine
with no luck. I hope someone can advice what is wrong.
This is the error I get:
[EMAIL PROTECTED]:~/WebKit$ Q
I am trying to build the QT port of WebKit on my Ubuntu 6.06 machine with no
luck. I hope someone can advice what is wrong.
This is the error I get:
[EMAIL PROTECTED]:~/WebKit$ QTDIR=/usr/share/qt4/
WebKitTools/Scripts/build-webkit
Calling 'qmake -r OUTPUT_DIR=/home/yael/WebKit/WebKitBuild/Relea
6 matches
Mail list logo
