Bug 16479 – kpopper doesn't emerge

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Paweł Sikora 2003-02-27 11:08:46 UTC]

when i try to emerge kpopper, i get errors about QT.
probably kpopper source isn't compatible with qt-3.1.x or gcc-3.2.x


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Thilo Bangert (RETIRED) (RETIRED) 2003-03-19 17:06:26 UTC]

is this a duplicat of bug #4788 ?? 
 
if so, please close this one... 
 
also, PLEASE give us some details here... 
 
thanks 
Thilo 

[Comment 2 Paweł Sikora 2003-03-20 18:55:50 UTC]

[...]

g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/kde/3.1/include -I/usr/qt/3/include -I/usr/X11R6/include   -DQT_THREAD_SUPPORT  -D_REENTRANT  -DNDEBUG -DNO_DEBUG -O2 -O3 -march=pentium3 -pipe -fomit-frame-pointer -fforce-addr -funroll-loops -fprefetch-loop-arrays -mfpmath=sse -s -z combreloc -fno-exceptions -fno-check-new  -c main.cpp
In file included from popper.cpp:36:
popupimpl.h:39:7: warning: no newline at end of file
In file included from popper.cpp:37:
newmsgimpl.h:47:7: warning: no newline at end of file
In file included from popper.cpp:38:
configdlgimpl.h:32:3: warning: no newline at end of file
In file included from popper.h:34,
                 from popper.cpp:40:
newmsgimpl.h:47:7: warning: no newline at end of file
popper.cpp:71: default argument given for parameter 3 of `void
   Popper::displayMessage(QString, QString, QString = "")'
popper.h:57: after previous specification in `void
   Popper::displayMessage(QString, QString, QString = "")'
In file included from popper.h:34,
                 from main.cpp:34:
newmsgimpl.h:47:7: warning: no newline at end of file
main.cpp: In function `void initConfig()':
main.cpp:54: choosing `const QString operator+(const QString&, char)' over `
   operator+'
main.cpp:54:   because worst conversion for the former is better than worst
   conversion for the latter
make[2]: *** [popper.o] Błąd 1
make[2]: *** Czekam na niezakończone zadania....
make[2]: *** [main.o] Błąd 1
make[2]: Leaving directory `/var/tmp/portage/kpopper-1.0/work/popper-1.0/popper'
make[1]: *** [all-recursive] Błąd 1
make[1]: Leaving directory `/var/tmp/portage/kpopper-1.0/work/popper-1.0'
make: *** [all-recursive-am] Błąd 2

!!! ERROR: net-misc/kpopper-1.0 failed.
!!! Function kde_src_compile, Line 116, Exitcode 2
!!! died running emake, kde_src_compile:make

[Comment 3 Dan Armak (RETIRED) 2003-03-22 15:01:38 UTC]

I've never seen wierd make output like this... What's "Błąd 1"? On second 
thought could that be encoding trouble? I can't go very without knowing what that means. 
Some of that should be the make error number, which is it? 
 
All the output above the make error is warnings, so the sourcefile itself doesn't seem to be 
problematic... 
 
What do the words in "Czekam na niezakończone zadania...." mean? 

[Comment 4 Dan Armak (RETIRED) 2003-03-22 15:02:17 UTC]

I meant, s/can't go very/can't go very far/. 

[Comment 5 Paweł Sikora 2003-03-26 13:42:13 UTC]

"Błąd" NLS(pl_PL.ISO-8859-2) = "Blad" = "Error". this is only "make" message :)

[Comment 6 Grant McDorman 2003-04-05 20:22:02 UTC]

I have developed a patch that fixes the compile errors. However,  
<A HREF="http://bugs.gentoo.org/show_bug.cgi?id=4788"> bug #4788 </a> then shows up. 
See that bug report - it is suggested that kpopper be dropped as an ebuild, and that one use 
kopete instead. 

[Comment 7 Grant McDorman 2003-04-05 20:23:18 UTC]

Created attachment 10241 [details, diff]
Patch to make kpopper compile (but not install).

[Comment 8 Paul de Vrieze (RETIRED) 2003-06-08 10:02:13 UTC]

Kpopper has been depreciated.