Date: Wed, 17 Jun 1998 18:27:54 -0500 From: "Kevin M. Dulzo" <kdulzo@internal.enteract.com> To: freebsd-questions@FreeBSD.ORG Subject: Recursive make calls in bsd.port.mk Message-ID: <19980617182754.A4295@internal.enteract.com>
next in thread | raw e-mail | index | archive | help
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? Thanks, -Kevin -- .-._.-. To see a thing uncolored by one's own personal preferences and desires is to see it in its own pristine simplicity. ._.-._. +==-- | Kevin M. Dulzo Check us out! | | System Administrator http://www.enteract.com | | Enteract, L.L.C. mailto: info@enteract.com| | kdulzo@enteract.com (773)248-8511 | --==+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980617182754.A4295>