From owner-freebsd-ports@FreeBSD.ORG Fri Jul 9 05:16:04 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B659D16A4CE for ; Fri, 9 Jul 2004 05:16:04 +0000 (GMT) Received: from sirius.firepipe.net (sirius.firepipe.net [69.13.116.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 741DE43D31 for ; Fri, 9 Jul 2004 05:16:04 +0000 (GMT) (envelope-from will@csociety.org) Received: by sirius.firepipe.net (Postfix, from userid 1000) id 14FC817F8A; Fri, 9 Jul 2004 00:16:04 -0500 (CDT) Date: Fri, 9 Jul 2004 00:16:04 -0500 From: Will Andrews To: Wesley Shields Message-ID: <20040709051604.GQ75771@sirius.firepipe.net> Mail-Followup-To: Wesley Shields , ports@freebsd.org References: <40ED8F1A.2000300@mac.com> <20040709021727.GA26453@csh.rit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="t5C3/nrmPumNj5sH" Content-Disposition: inline In-Reply-To: <20040709021727.GA26453@csh.rit.edu> User-Agent: Mutt/1.5.6i cc: ports@freebsd.org Subject: Re: Why does bsd.port.mk override make's search for Makefiles...? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2004 05:16:04 -0000 --t5C3/nrmPumNj5sH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 08, 2004 at 10:17:27PM -0400, Wesley Shields wrote: > On Thu, Jul 08, 2004 at 02:14:50PM -0400, Chuck Swiger wrote: >=20 > > As per the subject, why are these set in bsd.port.mk? > >=20 > > MAKE_FLAGS?=3D -f > > MAKEFILE?=3D Makefile > >=20 > > I was just trying to port something that had a "makefile" rather than a= =20 > > "Makefile", and was utterly baffled for a moment as to why make couldn'= t=20 > > find this. > >=20 > > --=20 > > -Chuck >=20 > Those are set because they are the defaults (almost all software uses > Makefile instead of makefile) but if you come across one that doesn't > just set this in your Makefile... That's the long-accepted solution, but it doesn't really answer his question. I thought about it and realized I had no idea of any make programs for which those defaults were necessary. However, sometimes ports DO need to use a nonstandard makefile name that is NOT searched by at least bmake and gmake. Perhaps the best thing to do might be to replace the b.p.m code: =2Eif defined(MAKE_FILE) MAKE_FLAGS?=3D -f ${MAKE_FILE} =2Eendif (Note this affects PR #30331[1], which I was working on some time ago and really need to finish.) [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/30331 Regards, --=20 wca --t5C3/nrmPumNj5sH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA7ioTF47idPgWcsURAkXHAJ9wI+J+z4f4acmbHGiDWeUUNDXGEACfWYmu 2QmYiZOq/X9K3Athnd8N4D8= =qsaE -----END PGP SIGNATURE----- --t5C3/nrmPumNj5sH--