From owner-freebsd-ports Fri Dec 15 12:52: 6 2000 From owner-freebsd-ports@FreeBSD.ORG Fri Dec 15 12:52:04 2000 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mothra.ecs.csus.edu (unknown [130.86.76.220]) by hub.freebsd.org (Postfix) with ESMTP id 0891737B400; Fri, 15 Dec 2000 12:52:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mothra.ecs.csus.edu (8.11.1/8.11.1) with ESMTP id eBFMIWX59171; Fri, 15 Dec 2000 14:18:32 -0800 (PST) (envelope-from joseph@randomnetworks.com) Date: Fri, 15 Dec 2000 14:18:32 -0800 (PST) From: Joseph Scott X-Sender: scottj@mothra.ecs.csus.edu To: Maxim Sobolev Cc: freebsd-ports@FreeBSD.ORG Subject: Re: Using HAS_CONFIGURE to enforce PREFIX In-Reply-To: <3A3A81E5.6F4A86F@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 15 Dec 2000, Maxim Sobolev wrote: # 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. Ahhh, HAS_CONFIGURE is much more generic then. I'm trying the follow all of the implies in bsd.port.mk in hopes that --prefix=${PREFIX} ends up in there. That doesn't seem to be the case. This begs the question, why doesn't GNU_CONFIGURE have a default arg of --prefix=${PREFIX} for gnu configure scripts? I guess this assumes that it will always understand --prefix use. Otherwise all ports that have GNU_CONFIGURE will also need CONFIGURE_ARGS+= --prefix=${PREFIX} yes? If I'm way off base in here simply invoke the pointy hat. *********************************************************** * Joseph Scott The Office Of Water Programs * * joseph@randomnetworks.com joseph.scott@owp.csus.edu * *********************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message