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