From owner-freebsd-current Mon Oct 18 1:38:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 760D214BF9 for ; Mon, 18 Oct 1999 01:38:46 -0700 (PDT) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial-lind-6.netcologne.de [195.14.250.6]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id KAA24095; Mon, 18 Oct 1999 10:38:43 +0200 (MET DST) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id KAA02398; Mon, 18 Oct 1999 10:38:59 +0200 (CEST) (envelope-from van.woerkom@netcologne.de) Date: Mon, 18 Oct 1999 10:38:59 +0200 (CEST) Message-Id: <199910180838.KAA02398@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: mnewell@newell.arlington.va.us Cc: freebsd-current@FreeBSD.ORG In-reply-to: (message from Mike Newell on Sun, 17 Oct 1999 16:38:53 -0400 (EDT)) Subject: Re: Signal 12 during build of -current Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm installing -current on a FreeBSD-3.3-stable system. I've done the sup > (which succeeded with no problems). When I try the "make buildworld" I > get "signal 12" crashes during the gcc lib build. In specific: I had the same problem (see my mail from 12th October). One of the present requirements is to build, install and boot the new kernel before doing the make world. Please read src/UPDATING, an excellent reference for major events in the source tree: 19990929: The sigset_t datatype has been changed from an integral type to a compound type and can hold 128 signals. Syscalls directly or indirectly using the new sigset_t have been added as to maintain compatible with existing binaries. A new kernel must be made and installed and booted with before a make world can be done. As you start from a v3 system, the v4 kernel might not work with v3 user land. I would suggest to grab an older v4 tree (e.g. as of September, 14th) and to move your v3 to that older v4 first. If this succeded, grab the latest v4 and try to jump over the sigset_t hurdle as described. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message