From owner-freebsd-ports Fri Apr 25 23:21:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08164 for ports-outgoing; Fri, 25 Apr 1997 23:21:28 -0700 (PDT) Received: from weychopee.shockwave.com (root@ppp-206-170-5-64.rdcy01.pacbell.net [206.170.5.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08157; Fri, 25 Apr 1997 23:21:20 -0700 (PDT) Received: from precipice.shockwave.com (precipice.shockwave.com [192.111.107.33]) by weychopee.shockwave.com (8.8.5/8.8.4) with SMTP id XAA24245; Fri, 25 Apr 1997 23:20:56 -0700 Message-Id: <3.0.1.32.19970425232055.0069f798@insecurity.shockwave.com> X-Sender: pst@insecurity.shockwave.com X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Fri, 25 Apr 1997 23:20:55 -0700 To: Bruce Evans From: Paul Traina Subject: Re: yale-tftpd build failure in -current Cc: asami@vader.cs.berkeley.edu, pst@freebsd.org, bde@zeta.org.au, ports@freebsd.org In-Reply-To: <199704250716.RAA20238@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:16 PM 4/25/97 +1000, Bruce Evans wrote: >>Could this have something to do with the recent *.mk file changes? If >>so, what is the fix, and is it going to be merged to 2.2? > >Seems unlikely. Ports makefiles don't use bsd.prog.mk or bsd.lib.mk, >right? I don't intend to merge anything except important bug fixes into >2.2. > >Bruce > > Sorry, ports makefiles /can and do/ use bsd.prog.mk. I've used it in a number of ports that were designed for 4.4BSD. In any case, it works perfectly under 2.2, and is only broken under 3.0, so someone must have broken 3.0 recently.