[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyKDE] [PyQt] PyQt-0.11 build failure
From: nbecker () fred ! net
Date: 2000-04-01 17:56:51
[Download RAW message or body]
> > > > > "Phil" == Phil Thompson <phil@river-bank.demon.co.uk> writes:
Phil> nbecker@fred.net wrote:
>>
>> gcc-2.95.2 i686-pc-linux-gnu qt-2.1.0beta3
>>
>> c++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python1.5 \
-I/usr/local/include/sip -I/usr/lib/qt-2.1.0/include -I/usr/X11R6/include \
-fno-exceptions -O2 -Wp,-MD,.deps/sipqtQWhatsThis.pp -c -fPIC -DPIC \
sipqtQWhatsThis.cpp -o sipqtQWhatsThis.lo >> sipqtQWhatsThis.cpp: In function \
`struct PyObject * sipDo_QWhatsThis_leaveWhatsThisMode(PyObject *, PyObject *)': >> \
sipqtQWhatsThis.cpp:717: initialization to `QString *' from `const QString *' \
discards qualifiers >> make[2]: *** [sipqtQWhatsThis.lo] Error 1
>> make[2]: Leaving directory `/usr/local/src/PyQt-0.11/qt'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/usr/local/src/PyQt-0.11'
>> make: *** [all-recursive-am] Error 2
Phil> Is this a problem with gcc 2.95? I use egcs 1.1.2 (2.91.66) where this
Phil> gives (I think) a warning, not an error.
I think it's not a problem, I think gcc-2.95.2 is correct that
discarding const is supposed to be an error. If you really want to
discard it you need const_cast.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic