From owner-freebsd-current Wed Oct 23 14:30:13 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 BE93C37B401; Wed, 23 Oct 2002 14:30:11 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C20AE43E65; Wed, 23 Oct 2002 14:30:10 -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 RAA00717; Wed, 23 Oct 2002 17:30:10 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9NLTeB09515; Wed, 23 Oct 2002 17:29:40 -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: <15799.5316.331108.803590@grasshopper.cs.duke.edu> Date: Wed, 23 Oct 2002 17:29:40 -0400 (EDT) To: Ruslan Ermilov Cc: current@FreeBSD.org, Alexander Kabaev Subject: Re: Groff problems (was Re: alpha tinderbox failure) In-Reply-To: <20021023180648.GA8656@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> <15798.56802.31765.434719@grasshopper.cs.duke.edu> <20021023180648.GA8656@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: > OK, to summarize things. There was a single problem with two > symptoms: 1) groff, if built dynamically, could not be run > by ld-elf.so; 2) groff, if built statically, always failed > with ``out of memory'', apparently due to the same bug. > > Static hack is safe to delete because: > > 1. groff that is built as part of the bootstrap-tools during > buildworld will be built static anyway (see -DNOSHARED in > BMAKE in Makefile.inc1) > > 2. if you have a vulnerable kernel and rtld-elf, static > linkage does not address the problem -- you get spurious > ``out of memory'' even if you link groff statically. > > If you agree, please feel free to commit the backout of > the hack yourself -- I'm going to leave the computer now. :-) Removed. Please review the following UPDATING entry: --- UPDATING 3 Sep 2002 06:13:43 -0000 1.217 +++ UPDATING 23 Oct 2002 21:24:44 -0000 @@ -22,6 +22,19 @@ integrity. Re-enabling write caching can substantially improve performance. +20021023: + Alphas with kernels from between 20020902 and 20021022 and/or + rtld (ld-elf.so.1) older than 20021022 may experience problems + with groff while doing a buildworld (kernel: "out of memory", + rtld: "too few PT_LOAD segments"). + + So, to successfully upgrade your Alpha, you must either + upgrade your kernel and rtld first (which might be a bit + tricky), or avoid running the bootstrapped groff during the + "transitional" buildworld. To avoid running groff during the + transitional upgrade run make buildworld with -DNOMAN, + -DNO_SHAREDOCS, and -DNO_LPR. + 20020831: gcc has been upgraded to 3.2. It is not all binary compatible with earlier versions of gcc for c++ programs. All c++ Note: I have NOT tested this, beyond verifying that a kernel from Sep 02 works fine. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message