From owner-freebsd-ports Fri Dec 15 13: 6:38 2000 From owner-freebsd-ports@FreeBSD.ORG Fri Dec 15 13:06:35 2000 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 17F9C37B404 for ; Fri, 15 Dec 2000 13:06:35 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.9.3/8.9.3) with SMTP id QAA86731; Fri, 15 Dec 2000 16:06:19 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <002901c066db$1e5ce7d0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Joseph Scott" Cc: References: <3A3A81E5.6F4A86F@FreeBSD.org> Subject: Re: Using HAS_CONFIGURE to enforce PREFIX Date: Fri, 15 Dec 2000 16:08:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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? In general, if a port uses GNU configure, then adding 'GNU_CONFIGURE=yes' to the Makefile is all that is neccessary. bsd.port.mk will look after passing the proper arguments to GNU configure to ensure that PREFIX is honored when the makefiles are built. Looking at security/stunnel, it defines USE_AUTOCONF, which implies GNU_CONFIGURE, which implies HAS_CONFIGURE, so this port should be honoring PREFIX in any case. As for ftp/cftp, it defines GNU_CONFIGURE which implies HAS_CONFIGURE and should honor PREFIX as well. Both of these ports built and installed properly for me using alternate values for PREFIX. One thing that you may be getting caught by is that you need to do a 'make clean' before trying to change the value of PREFIX for a port. This is because configure hard-codes the paths into the makefiles it builds during a 'make configure', and won't be updated if you do something like 'make install PREFIX=/some/other/dir' when you go to install. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message