Bug 217843

Summary:	net-wireless/kismet-2007.10.1 fails w/ gcc-4.3.0
Product:	Gentoo Linux	Reporter:	Peter Alfredsen (RETIRED) <loki_val>
Component:	[OLD] GCC Porting	Assignee:	Mobile Herd (OBSOLETE) <mobile+disabled>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alon.barlev, armin76, esigra, evan.teran, jlp.bugs, rose, teidakankan
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	198121
Attachments:	kismet-2007.10.1-gcc43.patch ebuild for gcc43 patch to kismet-2007.10.1

Description Peter Alfredsen (RETIRED) gentoo-dev

2008-04-15 19:48:10 UTC

i686-pc-linux-gnu-g++ -I/usr/src/linux -O2 -Wall -DVERSION_MAJOR=\"2007\" -DVERSION_MINOR=\"10\" -DVERSION_TINY=\"R1\" -DTIMESTAMP=\"`cat TIMESTAMP`\" -O2 -march=i686 -mtune=athlon-xp -msse -mmmx -pipe -ggdb3 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include   -c ringbuf.cc -o ringbuf.o
ringbuf.cc: In member function ‘int RingBuffer::InsertData(uint8_t*, int)’:
ringbuf.cc:60: error: ‘memcpy’ was not declared in this scope
ringbuf.cc:69: error: ‘memcpy’ was not declared in this scope
ringbuf.cc: In member function ‘void RingBuffer::FetchPtr(uint8_t*, int, int*)’:
ringbuf.cc:105: error: ‘memcpy’ was not declared in this scope
ringbuf.cc:110: error: ‘memcpy’ was not declared in this scope
ringbuf.cc:126: error: ‘memcpy’ was not declared in this scope
make: *** [ringbuf.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from util.cc:22:
util.h:68: warning: ‘typedef’ was ignored in this declaration
util.cc: In function ‘int Hex2UChar(unsigned char*, unsigned char*)’:
util.cc:116: error: ‘memset’ was not declared in this scope
make: *** [util.o] Error 1


Reproducible: Always

Steps to Reproduce:

Comment 1 Peter Alfredsen (RETIRED) gentoo-dev

2008-04-15 19:48:55 UTC

Created attachment 149839 [details, diff]
kismet-2007.10.1-gcc43.patch

Fixes the problem. Adapted from Debian.

Comment 2 avx 2008-06-12 12:53:23 UTC

(In reply to comment #1)
> Created an attachment (id=149839) [edit]
> kismet-2007.10.1-gcc43.patch
> 
> Fixes the problem. Adapted from Debian.
> 

Works for me with gcc4.3.1@ ~x86.

This patch is here now for about two months, please someone, get it into portage.

Comment 3 Evan Teran 2008-07-03 15:27:12 UTC

I second this notion, will this patch make it into portage any time soon?

Comment 4 A Frederick Christensen 2008-07-07 03:47:45 UTC

Created attachment 159760 [details]
ebuild for gcc43 patch to kismet-2007.10.1

I just made the same patch. That'll teach me to fix a bug before checking to see if anyone else has gotten around to it. Here's the modified ebuild though; maybe that'll push this a further toward the edge of the cliff where it can fall into portage.

Comment 5 Raúl Porcel (RETIRED) gentoo-dev

2008-08-11 11:44:38 UTC

*** Bug 234408 has been marked as a duplicate of this bug. ***

Comment 6 Raúl Porcel (RETIRED) gentoo-dev

2008-08-11 16:53:16 UTC

Added to 2008.05.1

Comment 7 Evan Teran 2008-08-11 19:14:56 UTC

Any chance that kismet-2008.05.1 will be in portage any time soon? Since that's the patched to work with gcc 4.3 version, it would be really nice if it worked it's way in there :-)

Comment 8 Raúl Porcel (RETIRED) gentoo-dev

2008-08-11 19:45:44 UTC

(In reply to comment #7)
> Any chance that kismet-2008.05.1 will be in portage any time soon? Since that's
> the patched to work with gcc 4.3 version, it would be really nice if it worked
> it's way in there :-)
> 

Uh, i mean i added 2008.05.1 to the tree with the gcc-4.3 patch...