Date: Fri, 15 Dec 2000 22:41:09 +0200 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Joseph Scott <joseph@randomnetworks.com> Cc: freebsd-ports@FreeBSD.org Subject: Re: Using HAS_CONFIGURE to enforce PREFIX Message-ID: <3A3A81E5.6F4A86F@FreeBSD.org> References: <Pine.BSF.4.21.0012151338490.58776-100000@mothra.ecs.csus.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Joseph Scott wrote:
> I've been updating a couple of ports and noticed something. Both
> of these ports use configure, but weren't honoring PREFIX. After looking
> through bsd.port.mk I came across HAS_CONFIGURE, who as a default of
> adding --prefix=${PREFIX} to the configure args. This made both of the
> ports in question correctly install into PREFIX instead of /usr/local.
>
> Is this the right way to enforce PREFIX with configure'd ports?
No, you are wrong. Unlike GNU_CONFIGURE, which assumes certain semantics of
configure scripts and therefore provides certain default command line arguments
for it, HAS_CONFIGURE is just plain hack to call a ${WRKSRC}/configure (it can
be anything from pre-compiled executable to the weird shell script) w/o any
additional arguments. Hovewer, you can add necessary flags into the appropriate
ports using CONFIGURE_ARGS make(1) variable.
-Maxim
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?3A3A81E5.6F4A86F>