From owner-freebsd-current  Fri Sep 25 15:44:19 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA28846
          for freebsd-current-outgoing; Fri, 25 Sep 1998 15:44:19 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28839
          for <current@FreeBSD.ORG>; Fri, 25 Sep 1998 15:44:13 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA05815;
	Sat, 26 Sep 1998 08:44:04 +1000
Date: Sat, 26 Sep 1998 08:44:04 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199809252244.IAA05815@godzilla.zeta.org.au>
To: current@FreeBSD.ORG, jkh@time.cdrom.com
Subject: Re: Another interesting build anomaly just noticed in -current
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Observe the output below carefully.  Erm.  We're actually applying
>patches during the build process?  Since when was that considered
>a reasonable thing to do? :-)

Since I considered it.  The changes can't just be checked into
contrib_libreadline since they are for noncontrib_gdb.  Maintaining
a separate file in gdb tended to get out of date whenever either
contrib_libreadline or contrib_gdb was updated.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message