I am having trouble getting either nessus-1.0.7a-r1 or nessus-1.0.9.ebuild to build. For nessus-1.0.7a-r1, I get: gcc -pipe -I../libpeks -DHAVE_CONFIG_H -DENABLE_CRYPTO_LAYER -I/usr/include/peks -I. -I/usr/include -I/var/tmp/portage/nessus-1.0.7a-r1/work/nessus-libraries/include -I/var/tmp/portage/nessus-1.0.7a-r1/work/nessus-libraries/libpcap-nessus -mcpu=k6 -march=k6 -O3 -pipe -c network.c -fPIC -DPIC -o .libs/network.lo gcc: Internal compiler error: program cc1 got fatal signal 11 make[1]: *** [network.o] Error 1 make[1]: Leaving directory `/var/tmp/portage/nessus-1.0.7a-r1/work/nessus-libraries/libnessus' make: *** [all] Error 2 !!! ERROR: the make command did not complete successfully. !!! ("make") !!! Since this is a critical task, ebuild will be stopped. !!! emerge aborting on /usr/portage/net-analyzer/nessus/nessus-1.0.7a-r1.ebuild . root@stkilda nessus # cpp0: output pipe has been closed For nessus-1.0.9 I get: gcc -mcpu=k6 -march=k6 -O3 -pipe `./cflags` -c sighand.c sighand.c: In function `let_em_die': sighand.c:49: `WNOHANG' undeclared (first use in this function) sighand.c:49: (Each undeclared identifier is reported only once sighand.c:49: for each function it appears in.) make[1]: *** [sighand.o] Error 1 make[1]: Leaving directory `/var/tmp/portage/nessus-1.0.9/work/nessus-core/nessusd' make: *** [server] Error 2 However, if you tell portage to emerge the package AGAIN, it gets further in the compilation: /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -c -m 0444 include/nessustcp.h /var/tmp/portage/nessus-1.0.9/image//usr/include/nessus /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -c -m 0444 include/nessusudp.h /var/tmp/portage/nessus-1.0.9/image//usr/include/nessus /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -m 755 nessus-adduser /var/tmp/portage/nessus-1.0.9/image//usr/sbin installing man pages ... /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -c -m 0444 doc/nessus-cipher.1 /var/tmp/portage/nessus-1.0.9/image//usr/share/man/man1/nessus.1 /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -c -m 0444 doc/nessusd-cipher.8 /var/tmp/portage/nessus-1.0.9/image//usr/share/man/man8/nessusd.8 /var/tmp/portage/nessus-1.0.9/work/nessus-core/install-sh -c -c -m 0444 doc/nessus-adduser.8 /var/tmp/portage/nessus-1.0.9/image//usr/share/man/man8/nessus-adduser.8 -------------------------------------------------------------- nessus-core has been sucessfully installed. Make sure that /var/tmp/portage/nessus-1.0.9/image//usr/bin and /var/tmp/portage/nessus-1.0.9/image//usr/sbin are in your PATH before you continue. nessusd has been installed into /var/tmp/portage/nessus-1.0.9/image//usr/sbin -------------------------------------------------------------- Compiling plugins... creating cache ./config.cache checking host system type... i586-pc-linux-gnu checking for ranlib... ranlib checking for gcc... gcc checking whether the C compiler (gcc -mcpu=k6 -march=k6 -O3 -pipe ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. Makefile:1: nessus.tmpl: No such file or directory make: *** No rule to make target `nessus.tmpl'. Stop. This may be related to a bug which a posted wrt building Mozilla (bug #332), or building Perl (bug #458... also missing from Bugzilla. The comment in the Mozilla bug that it's "bad memory" is spurious in that it doesn't explain why other complex packages (like the Linux Kernel, or X) build without a hitch. Here is my USE from make.conf: USE="slang readline gpm berkdb gdbm tcpd pam libwww ssl alsa nls mitshm perl python esd gif sdl vorbis ogg gnome gtk X qt kde motif opengl mozilla objprelink cups mmx 3dnow java guile mysql tex bonobo libg++ tcltk lame" and some additional parameters from further in the make.conf: CHOST="i586-pc-linux-gnu" CFLAGS="-mcpu=k6 -march=k6 -O3 -pipe" CXXFLAGS="-mcpu=k6 -march=k6 -O3 -pipe"
again, if you are getting random compilation failures, it's most likely due to bad memory. Until you have verified that your memory is ok using "memtest86", I will be marking these bug reports as "WORKSFORME". Thomas, fatal sig 11's that occur randomly during compilation are and almost sure sign of a hardware problem. If it were a software problem, the build would die in the exact same place every time.
>Humiliation< Damn. You gotta believe that not 3 weeks ago I tested the system and it was clean. That having been said, this time memtest v2.8 tells me the memory is fubar. Grrr. So I've replaced the RAM, and tested the new. Clean. (for now... seems that current status is no guarantee of future performance). An Nessus builds without breaking a sweat. Sorry for wasting your time on this one. BTW: the memprof bug is not related to the memory problem. It fails consistently at the same point each time (bug #417). Thanks again for all your help!
