Emerging kismet fails. See http://valhalla.thorshammer.org/kismet.fullerror for full capture of the emerge. ... cut ... g++ -Ilibpcap-2002.12.23 -O2 -Wall -DVERSION_MAJOR=2 -DVERSION_MINOR=8 -DVERSION_TINY=1 -DTIMESTAMP=\"`cat TIMESTAMP`\" -march=i686 -O3 -march=i686 -O3 -c panelfront_display.cc -o panelfront_display.o g++: Internal error: Terminated (program cc1plus) Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. make: *** [kismet_server.o] Error 1 make: *** Waiting for unfinished jobs.... !!! ERROR: net-wireless/kismet-2.8.1-r1 failed. !!! Function src_compile, Line 59, Exitcode 2 !!! compile of kismet failed Reproducible: Always Steps to Reproduce: 1. emerge kismet 2. wait for panelfront_display.o to build 3. Error is produced, emerge exits Actual Results: Emerge exits with an error. Expected Results: Installed kismet. Please let me know what other information you need to help troubleshoot this problem (hardware config, software config, etc) or if I have made an error when emerging kismet.
Internal compiler errors are typically a hardware problem (see bug #20600). You may want to check your CPU cooling and your RAM. (How much RAM does this box have?)
This is on an IBM Thinkpad 600 w/ 128M ram and ~84M swap. I was just able to install Kismet from the tarball, so maybe the CFLAGS passed in emerge are too much... Currently I have "-march=i686 -O3". PS. Is there a way to tell portage/emerge that I have this installed? Thanks.
Check out the 'inject' option in the man page for emerge.
I don't think it's a hardware problem, as I have exactly the same effect when I try to emerge kismet. I had no problem with other emerges yet. My CFLAGS are "march=pentium-mmx -O3".
Is this problem still present with net-wireless/kismet-2004.10.1?
Changing to NEEDINFO.
Closing due to lack of feedback.
