From owner-freebsd-current Wed Oct 23 10:36: 2 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 74A8B37B40D; Wed, 23 Oct 2002 10:36:01 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADFD843E3B; Wed, 23 Oct 2002 10:36:00 -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 NAA17562; Wed, 23 Oct 2002 13:36:00 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9NHZUi09280; Wed, 23 Oct 2002 13:35:30 -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.56802.31765.434719@grasshopper.cs.duke.edu> Date: Wed, 23 Oct 2002 13:35:30 -0400 (EDT) To: Ruslan Ermilov Cc: current@FreeBSD.org Subject: Re: Groff problems (was Re: alpha tinderbox failure) In-Reply-To: <20021023142044.GD31781@sunbay.com> References: <200210210942.g9L9gLpM025724@beast.freebsd.org> <15796.17145.909288.498725@grasshopper.cs.duke.edu> <20021022142929.GB48398@sunbay.com> <20021022220221.3a8e2312.kabaev@bellatlantic.net> <15798.43826.90549.275914@grasshopper.cs.duke.edu> <20021023142044.GD31781@sunbay.com> 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 Ruslan Ermilov writes: > Nice. I was going to ask Peter to upgrade beast with this fix, but > now that you've already tested it, I'd like to back out the hack in > groff/src/roff/groff/Makefile, if there are no objections. OK.. with the new rtld, a shared groff works. Before you backout the static hack, can you explain the upgrading implications? Since both a new rtld and a new kernel are required to be able to buildworld from an alpha older than yesterday, do we just note that in UPDATING, or do we somehow build groff statically in the early phase, so that a the early stages of buildworld will not depend on having a updated rtld? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message