From owner-freebsd-current Thu Oct 24 6:44:49 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 8007A37B401; Thu, 24 Oct 2002 06:44:46 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id A08B243E65; Thu, 24 Oct 2002 06:44:39 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g9ODiLJ74004; Thu, 24 Oct 2002 16:44:21 +0300 (EEST) (envelope-from ru) Date: Thu, 24 Oct 2002 16:44:21 +0300 From: Ruslan Ermilov To: Andrew Gallatin Cc: current@FreeBSD.org, Alexander Kabaev , Peter Wemm Subject: Re: Groff problems (was Re: alpha tinderbox failure) Message-ID: <20021024134421.GA71665@sunbay.com> References: <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> <15799.5316.331108.803590@grasshopper.cs.duke.edu> <20021024074158.GA94686@sunbay.com> <15799.61882.81170.404538@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <15799.61882.81170.404538@grasshopper.cs.duke.edu> User-Agent: Mutt/1.3.99i 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 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 24, 2002 at 09:12:26AM -0400, Andrew Gallatin wrote: >=20 > Ruslan Ermilov writes: > <...> > > > +20021023: > > > + Alphas with kernels from between 20020902 and 20021022 and/or > > > + rtld (ld-elf.so.1) older than 20021022 may experience proble= ms > > > + 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 compatib= le > > > with earlier versions of gcc for c++ programs. All c++ > > >=20 > > >=20 > > > Note: I have NOT tested this, beyond verifying that a kernel from S= ep > > > 02 works fine. > > >=20 > > What commit is responsible for a breakage, this one? > >=20 > > : peter 2002/09/03 14:18:17 PDT > > :=20 > > : Modified files: > > : sys/kern imgact_elf.c > > : Log: > > : Make the text segment locating heuristics from rev 1.121 more reli= able > > : so that it works on the Alpha. This defines the segment that the = entry >=20 >=20 > More or less.. The data, text and vmem limit checking in general. > Matt's initial commit on 20020830 broke Alpha totally, so the earliest > kernel that would both exhibit the problem and could get to the point of > attempting to build world would be from 20020903. I'll update > my proposed UPDATING entry with the 20020903 date so as to be more > exact. Assuming I do that, do you agree that its accurate enough to > be helpful? >=20 Yes. It may be worth specifying which files/revisions are responsible for a fix -- it might be useful for those who attempt to fix their kernel/rtld first. One thing I'm still missing is why groff binary now comes with only one PT_LOAD segment, and why this is Alpha specific? And why if I checkout old, -D2002/10/10 contrib/groff and gnu/usr.bin/groff and compile gnu/usr.bin/groff/src/roff/groff on the same machine (I tried it on beast.freebsd.org), it produces two PT_LOAD segments? (These are actually two things.) 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) iD8DBQE9t/k1Ukv4P6juNwoRAmNjAJ9bN0V7vtm2vc1npozH5JHsCD8a4gCfaFhK l2MVhWyVxO6k+BODhpf7MgE= =A2lC -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message