Summary: | emerge kismet (2.8.1-r1) fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | robert |
Component: | New packages | Assignee: | Peter Johanson (RETIRED) <latexer> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | CC: | avenj, mobile+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://valhalla.thorshammer.org/kismet.fullerror | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
robert
2003-07-13 14:21:05 UTC
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. |