Date: Wed, 7 Aug 2002 16:14:28 +0200 From: Roman Neuhauser <neuhauser@bellavista.cz> To: MikeM <MyRaQ@mgm51.com> Cc: freebsd-questions@FreeBSD.org Subject: Re: How to pass configure parms into a port Message-ID: <20020807141428.GO281@freepuppy.bellavista.cz> In-Reply-To: <200208071007280479.03E5A1A4@sentry.24cl.com> References: <200208061115140503.0049FE96@sentry.24cl.com> <20020806152707.GB281@freepuppy.bellavista.cz> <200208070920250907.03BA8FFB@sentry.24cl.com> <20020807133152.GM281@freepuppy.bellavista.cz> <200208071007280479.03E5A1A4@sentry.24cl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Wed, 07 Aug 2002 10:07:28 -0400
> From: "MikeM" <MyRaQ@mgm51.com>
> To: neuhauser@bellavista.cz
> Cc: freebsd-questions@FreeBSD.org
> Subject: Re: How to pass configure parms into a port
>
> On 8/7/02 at 3:31 PM Roman Neuhauser wrote:
> >
> > this is covered in make(1), which i think you've read seeing you
> > knew how to get the value of CONFIGURE_ARGS from it.
> >
> > ...
> >
> >> So the command line invocation of CONFIGURE_ARGS seems to work as
> >> expected. Cool. I'll send a note to the handbook folk, and ask if
> >> this can be added to the ports section of the handbook.
> >
> > documentation never killed anybody. :)
> =============
>
> Yup. The handbook was the first place I looked for the answer. Once I
> got into the bsd.port.mk file and make(1), I ran into information
> overload; and I missed something obvious, as you noted above. :-)
this i can understand. :)
> Thanks for the follow-up.
no problem.
--
FreeBSD 4.6-STABLE
4:13PM up 23:33, 10 users, load averages: 0.04, 0.06, 0.02
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?20020807141428.GO281>