Date: Wed, 23 Oct 2002 17:29:40 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: current@FreeBSD.org, Alexander Kabaev <kan@FreeBSD.org> Subject: Re: Groff problems (was Re: alpha tinderbox failure) Message-ID: <15799.5316.331108.803590@grasshopper.cs.duke.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15799.5316.331108.803590>