Date: Thu, 18 Jun 1998 14:26:48 -0600 (MDT) From: Brett Taylor <brett@peloton.physics.montana.edu> To: kdulzo@enteract.com Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Recursive make calls in bsd.port.mk Message-ID: <Pine.BSF.3.96.980618142507.7108E-100000@peloton.physics.montana.edu> In-Reply-To: <19980617182754.A4295@internal.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
(cc'd to ports instead of questions) On Wed, 17 Jun 1998, Kevin M. Dulzo wrote: > It appears that when you use an alternative makefile ala 'make > -f', it doesn't affect any further make calls that bsd.port.mk use; it > will reuse the default 'Makefile'. This makes sense in some ways, but > a 'make -n' DOES get passed on... Is there any rhyme or reason to > this? I'd really like to specify alternate makefiles for a > consolidated ports tree for multiple machines, this is a small thorn > =). The port I tried was www/lynx; all I needed was to drop the > --with-zlib from configure arguments...I know numerous ways around > this issue, but I wondered why -n would pass and -f would not. Is > this a bug in the mk file or just a wierd effect? You can set the makefile to be something different by defining, in the port makefile: MAKEFILE= name_of_the_makefile_you_want_to_use (I'm not sure if this is what you wanted to know) Brett ********************************************************* Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980618142507.7108E-100000>