From owner-freebsd-current Wed Oct 23 6:59:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8886237B401; Wed, 23 Oct 2002 06:59:45 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8766243E6E; Wed, 23 Oct 2002 06:59:44 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA03230; Wed, 23 Oct 2002 09:59:44 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9NDxEs09051; Wed, 23 Oct 2002 09:59:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15798.43826.90549.275914@grasshopper.cs.duke.edu> Date: Wed, 23 Oct 2002 09:59:14 -0400 (EDT) To: ak03@gte.com Cc: Ruslan Ermilov , kan@FreeBSD.org, obrien@FreeBSD.org, current@FreeBSD.org Subject: Re: Groff problems (was Re: alpha tinderbox failure) In-Reply-To: <20021022220221.3a8e2312.kabaev@bellatlantic.net> References: <200210210942.g9L9gLpM025724@beast.freebsd.org> <15796.17145.909288.498725@grasshopper.cs.duke.edu> <20021022142929.GB48398@sunbay.com> <20021022220221.3a8e2312.kabaev@bellatlantic.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alexander Kabaev writes: > I hope this problem is fixed now. Let me know if I am sadly mistaken > about that :) Thanks! It seems to fix it when building groff directly from the src directory (eg, after your kernel change, yesterday's binaries work). I'm building the world now. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message