From owner-freebsd-current Tue Jan 2 14:28:11 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:28:04 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 09D6837B402 for ; Tue, 2 Jan 2001 14:28:04 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f02MRkq53305; Tue, 2 Jan 2001 23:27:46 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Matthew Jacob , Warner Losh , Charlie Root , current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: Your message of "Tue, 02 Jan 2001 14:17:41 PST." <200101022217.f02MHfX57879@earth.backplane.com> Date: Tue, 02 Jan 2001 23:27:46 +0100 Message-ID: <53303.978474466@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101022217.f02MHfX57879@earth.backplane.com>, Matt Dillon writes: > >:Ta-da! >: >: >:> In message Matthew Jacob writes: >:> : Same with me. >:> >:> This sounds like a job for Captain UPDATING: >:> >:> 20010101: >:> ex and vi were broken by some changes to sys/queue.h. If >:> you have a bad vi (and are getting core dumps when building >:> termcap), you can work around this problem by adding -k to >:> your command line. This will cause the build to complete >:> and install a new vi. Once that's done, you can rebuild again >:> without the -k to pick up anything that might have been >:> ignored by the -k option. > > Why in (insert favorite deity)'s name does ex and vi depend on > sys/queue.h ? Actually they don't, they depend on db1.85's "mpool" which depends on since it lives in libc. vi/ex comes with their own copy of -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message