From owner-freebsd-current Thu Jan 25 11:13:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id C175237B6AD; Thu, 25 Jan 2001 11:12:56 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id ED0DEAE3; Thu, 25 Jan 2001 11:12:55 -0800 (PST) Received: from cup.hp.com (gauss.cup.hp.com [15.28.97.152]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id LAA27469; Thu, 25 Jan 2001 11:12:55 -0800 (PST) Message-ID: <3A707AB7.53C0BB11@cup.hp.com> Date: Thu, 25 Jan 2001 11:12:55 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ruslan Ermilov Cc: rene@xs4all.nl, stable@FreeBSD.org Subject: Re: Bootstrapping issues with groff(1) References: <20001216171526.A28853@sunbay.com> <20010124182729.A22713@xs4all.nl> <20001208181908.A12716@sunbay.com> <3A319751.D2C9E5AB@cup.hp.com> <20001209154347.A78374@sunbay.com> <3A329641.CC6D8447@cup.hp.com> <20001211094815.D96665@sunbay.com> <3A3509E9.F1D19305@cup.hp.com> <20001212102344.B92312@sunbay.com> <3A3663DB.2DA71F0E@cup.hp.com> <20010125142504.A15489@sunbay.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I don't know why -current is CC'd this is clearly about -stable] Ruslan Ermilov wrote: > > Attached is the patch for RELENG_4. It works but I don't like > how it pollutes the Makefile.inc1. Anyone with a better idea? Allow me to sidetrack for a moment: I just ugraded a machine from 4.1 to 4.2-stable without any problems. I'm a bit confused. Rene picks up RELENG_4 and sees his build fail. Why did it work for me? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message