From owner-freebsd-questions Tue Jun 19 8:52:38 2001 Delivered-To: freebsd-questions@freebsd.org Received: from nebula.anchoragerescue.org (cable-115-7-237-24.anchorageak.net [24.237.7.115]) by hub.freebsd.org (Postfix) with ESMTP id 4830D37B401 for ; Tue, 19 Jun 2001 08:52:28 -0700 (PDT) (envelope-from akbeech@anchoragerescue.org) Received: from galaxy.anchoragerescue.org (galaxy.anchoragerescue.org [24.237.7.95]) by nebula.anchoragerescue.org (Postfix) with SMTP id 1E5C2183; Tue, 19 Jun 2001 07:52:27 -0800 (AKDT) Content-Type: text/plain; charset="iso-8859-1" From: Beech Rintoul To: Gregory W Lovell , freebsd-questions@freebsd.org Subject: Re: Failed "make" on quite normal kernel Date: Tue, 19 Jun 2001 07:52:26 -0800 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01061907522600.64018@galaxy.anchoragerescue.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday 18 June 2001 23:34, Gregory W Lovell wrote: > FreeBSD Questions, > > I've tried to recompile the kernel to add NATD support to my system 3 > times now, and it has failed every time. The only change I have made to > the config file when compared to GENERIC are adding the lines: > > options IPFIREWALL > options IPDIVERT > > These are added at the end of all the other "options" lines. > > The last few lines shown after the make command crashes are: > > si -nostdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include > opt_global.h -e > lf -mpreferred-stack-boundary=2 ../../dev/nsp/nsp.c > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > > Stop in /usr/src/sys/compile/NATD > bash-2.05#cpp:output pipe has been closed > Jun 19 07:06:52 /kernel:pid 6420(cc1), uid 0: exited on signal 11 (core > dumped) > > As you can imagine, this is quite frustrating, as NATD is to be one of the > primary functions of the box. It is a Pentium 133 on a SuperMicro board > without FDD, Serial or Parallel Controllers. Everything else seems to > work fine except this. One thing that may be worth noting is that I > actually have installed FreeBSD by plugging the HDD into another computer, > as I cannot boot from CD-ROM or FDD. I was told this would be OK, but you > never know... > > Any help would be greatly appreciated. The rest of my experience with > FreeBSD has been very positive. > > Greg Lovell Sig 11 is a sign of hardware failure, usually memory. Check the maillist as his issue comes up regularly. Beech ------------------------------------------------------------------- Beech Rintoul - IT Manager - Instructor - akbeech@anchoragerescue.org /"\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message