Date: Fri, 15 Dec 2000 22:59:39 -0500 From: "Matthew Emmerton" <matt@gsicomp.on.ca> To: "Joseph Scott" <joseph@randomnetworks.com> Cc: <freebsd-ports@FreeBSD.ORG> Subject: Re: Using HAS_CONFIGURE to enforce PREFIX Message-ID: <002a01c06714$9d6ce460$1200a8c0@gsicomp.on.ca> References: <Pine.BSF.4.21.0012151444560.58776-100000@mothra.ecs.csus.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hummmm, I tried a `make install PREFIX=/tmp/port` and in some > cases all of the port would still go to /usr/local, in others only part > would go to PREFIX, the rest to /usr/local. There's actually a good reason for this! Let's use ftp/cftp as an example. When you do a 'make configure', GNU configure will embed the given value of PREFIX into all the makefiles it generates. Thus, when you do a 'make install', it will install using the value of PREFIX that was given at configure-time, and ignore the one given on the 'make install' command line. However, this port has a post-install target in the main Makefile, which uses PREFIX as well. However, note that the post-install target will use the value of PREFIX given on the command line, even though it may differ from the one given to the configure target when the port was originally built. This is why you could get files installed into both /usr/local and /some/other/dir from one port. -- Matt Emmerton 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?002a01c06714$9d6ce460$1200a8c0>