Date: Wed, 23 Oct 2002 21:06:48 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.org, Alexander Kabaev <kan@FreeBSD.org> Subject: Re: Groff problems (was Re: alpha tinderbox failure) Message-ID: <20021023180648.GA8656@sunbay.com> In-Reply-To: <15798.56802.31765.434719@grasshopper.cs.duke.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Oct 23, 2002 at 01:35:30PM -0400, Andrew Gallatin wrote:
>=20
> 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.
>=20
> OK.. with the new rtld, a shared groff works.
>=20
> Before you backout the static hack, can you explain the upgrading
> implications?
>=20
> 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?
>=20
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. :-)
So, to successfully upgrade your Alpha, you must either
upgrade your kernel and rtld first (which might be a bit
tricky), or to avoid running the bootstrapped groff during
the "transitional" buildworld. All consumers of groff
are manpages and share/doc documents, with only one nasty
exception -- usr.sbin/lpr/SMM.doc/Makefile, so it should
be possible to buildworld with -DNOMAN, -DNO_SHAREDOCS,
and -DNO_LPR to achieve this -- avoid running groff during
the transitional upgrade.
PS.
Someone could tell me what is different with Alpha so
that it produces only one PT_LOAD segment, compared
to i386? Just wondering...
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE9tuU4Ukv4P6juNwoRAn+OAJwOA6ymrLNmKh4Bp5IeNdPG2Z+6zQCffHd0
glT1SDormpfXizyAEKao/5Y=
=6cXt
-----END PGP SIGNATURE-----
--M9NhX3UHpAaciwkO--
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?20021023180648.GA8656>