Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 133535 (klibido) - net-nntp/klibido or 0.2.5 does not build with gcc 4.1.0-r1
Summary: net-nntp/klibido or 0.2.5 does not build with gcc 4.1.0-r1
Alias: klibido
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GCC Porting (show other bugs)
Hardware: x86 Linux
: Highest normal (vote)
Assignee: Gentoo Net-news project
Keywords: QAcanfix
Depends on:
Blocks: 117482
  Show dependency tree
Reported: 2006-05-16 13:49 UTC by Jorg Pitts
Modified: 2006-12-09 10:31 UTC (History)
13 users (show)

See Also:
Package list:
Runtime testing required: ---

patch from debian sid against 0.2.5 klibido to fix gcc 4.1.x compiles (11_ftbfs_with_gcc_4_1.diff,1.07 KB, text/x-patch)
2006-05-31 12:27 UTC, Jorg Pitts
ebuild for gcc 4.1 (no use flag, no detection, beware...) (klibido-0.2.5.ebuild,964 bytes, text/plain)
2006-09-07 13:02 UTC, El Goretto

Note You need to log in before you can comment on or make changes to this bug.
Description Jorg Pitts 2006-05-16 13:49:02 UTC
compiled fine with gcc 3.4.6
compile failure when compiling with gcc 4.1.0

i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/kde/3.5/include -I/usr/qt/3/include -I.  -I/usr/kde/3.5/include -I/usr/include/db4  -DQT_THREAD_SUPPORT  -D_REENTRANT -I/include  -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -DNDEBUG -DNO_DEBUG -O2 -O2 -march=athlon-xp -pipe -I/usr/include/db4.2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -fexceptions  -c -o main.o main.cpp
nntpthreadsocket.h:237: error: extra qualification 'NntpThreadSocket::' on member 'm_findEndLine'
yydecoder.h:90: error: extra qualification 'yyDecoder::' on member 'charCRC'
make[2]: *** [main.o] Error 1
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-05-16 13:57:13 UTC
- Don't touch the restrict checkboxes if you have no clue what they are used for.
- Don't mark bugs as P1 blocker unless your whole system is completely unusable.
Comment 2 ignoreme 2006-05-31 11:08:36 UTC
I am also receiving this error with GCC 4.1.1 looking at Klibido's site there is a patch for this issue.

I have attempted to use this patch with Klibido but was unsuccessful, but it was probably an error on my end, since I've never done this before.

This patch also might work with 0.2.5 as well.
Comment 3 Jorg Pitts 2006-05-31 12:27:39 UTC
Created attachment 88021 [details]
patch from debian sid against 0.2.5 klibido to fix gcc 4.1.x compiles

This patch works for me
Comment 4 ignoreme 2006-05-31 16:15:22 UTC
From looking at the patch supplied on sourceforge I don't think it can be applied to, unless it is modifed.  I will try it out on 0.2.5 as well.
Comment 5 ignoreme 2006-05-31 16:33:12 UTC
Using the 0.2.5 ebuild from and applying this patch I was able to sucesfully build klibido 0.2.5 with no extra steps.
Comment 6 Guy 2006-08-26 21:26:09 UTC
This works for me.

Could this patch be added to portage soon?
Comment 7 ra 2006-09-07 06:04:17 UTC
The patch is very important and needs to be added to portage ASAP, since you cannot compile this at all with a 2006.1 profile.

Please mark this bug as critial.
Comment 8 El Goretto 2006-09-07 13:02:24 UTC
Created attachment 96315 [details]
ebuild for gcc 4.1 (no use flag, no detection, beware...)

Only for impatients, and lazy people like me...
Comment 9 El Goretto 2006-09-07 13:04:38 UTC
Ooops, sorry I didnt know all was send when adding an attachment.
Juste copy and rename the already joined patch to "0.2.5-ftbfs_with_gcc_4_1.patch".
And maybe adding a "--digest" option when emerging.
Comment 10 Erik Logtenberg 2006-09-18 10:18:50 UTC
This patch works for me too. I suggest putting it in portage, since it won't compile at all without this patch.
Comment 11 moesasji 2006-09-23 23:54:25 UTC
This was the second time that I hit this bug. 
Klibido does NOT compile for systems using GCC 4.1, which is now considered stable. It has been in this state for >4 months. 

At the same time a working patch is present for almost 4 months as confirmed by the posts here. If tried it both on ~x86 and ~amd64 and it compiles and works with that patch. So could somebody please fix this package in the tree??
Comment 12 Christian Heim (RETIRED) gentoo-dev 2006-09-30 06:07:22 UTC
Sven, could you please look into this ?
Comment 13 Aniruddha 2006-10-01 09:46:13 UTC
Is this bug already fixed? If not, how do I apply the patch manually? Thanks in advance!
Comment 14 Charlie Shepherd (RETIRED) gentoo-dev 2006-10-08 22:51:41 UTC
This should block bug 117482
Comment 15 Jakub Moc (RETIRED) gentoo-dev 2006-11-18 02:15:37 UTC
*** Bug 155555 has been marked as a duplicate of this bug. ***
Comment 16 Ryan Hill (RETIRED) gentoo-dev 2006-12-09 10:31:27 UTC
fixed in ~arch by bug #124987.  stable bug is #155555.