From owner-freebsd-questions Wed Jun 17 16:28:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02193 for freebsd-questions-outgoing; Wed, 17 Jun 1998 16:28:08 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from caffeine.internal.enteract.com (qmailr@caffeine.internal.enteract.com [207.229.129.24]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA02067 for ; Wed, 17 Jun 1998 16:27:59 -0700 (PDT) (envelope-from kdulzo@caffeine.internal.enteract.com) Received: (qmail 4305 invoked by uid 100); 17 Jun 1998 23:27:54 -0000 Message-ID: <19980617182754.A4295@internal.enteract.com> Date: Wed, 17 Jun 1998 18:27:54 -0500 From: "Kevin M. Dulzo" To: freebsd-questions@FreeBSD.ORG Subject: Recursive make calls in bsd.port.mk Reply-To: kdulzo@enteract.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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