[woody kde3 and sarge with gcc 3.3 is not a perfect solution]
Thanks for all your replys. I have to think about that issue. I dont like to
move to sid with all of my kde stuff, so I try to move to gcc295 for a
while.
BTW what is the reason for KDE not to step ahaed to testing? I am going to
have
On 07.Jul 2003 - 20:14:32, Thomas Watz wrote:
> Hello,
>
> I have some probs with compiling KDE/QT progs since going to KDE 3.1.
>
> I tried to compile sim 0.82 and got the following failure message:
>
> [...]
> checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not
> found. P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 07 Jul 2003 19:14, Thomas Watz <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have some probs with compiling KDE/QT progs since going to KDE 3.1.
>
> I tried to compile sim 0.82 and got the following failure message:
>
> [...]
> checking for Qt...
GCC 2.95 and GCC 3.3 don't play well together.
Sarge is using Gcc 3.3 as the default compiler, but if you're using the woody
KDE packages, these are compiled using gcc 2.95.
You will need to use gcc 2.95 to compile KDE programs until the sid KDE
packages filter into sarge.
David
On Monday 07 J
Hello,
I have some probs with compiling KDE/QT progs since going to KDE 3.1.
I tried to compile sim 0.82 and got the following failure message:
[...]
checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not
found. Please check your installation!
For more details about this probl
5 matches
Mail list logo
