Date: Mon, 13 Jun 2005 19:57:28 +0200 From: =?UTF-8?B?S8O2dmVzZMOhbiBHw6Fib3I=?= <gabor.kovesdan@t-hosting.hu> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Makefile question Message-ID: <42ADC908.6060505@t-hosting.hu> In-Reply-To: <20050613174248.GA85674@dan.emsphone.com> References: <42ADC155.10304@t-hosting.hu> <20050613174248.GA85674@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh, I didn't mean that. Both the configure script and the application Makefile are working. What I mean is, that the configure script doesn't let me to specify --libdir, --bindir, ... Thus a lot of files would be installed directly under the default ${PREFIX}, which is /usr/local, that's why I would like to specify a separated subdirectory under the ${PREFIX}, but my CONFIGURE_ARGS=--prefix=${PREFIX}/appname doesn't work, but I don't know why. I thought it is syntactically correct, but it had the same effect as is I wrote only ${PREFIX} instead of ${PREFIX}/appname. Cheers, Gábor Kövesdán Dan Nelson wrote: >Maybe the problem is not the configure script but the Makefile install >target. Check to see what the generated Makefile looks like. It's >possible that it uses gnumake syntax, in which case you may need >USE_GMAKE=yes in the port Makefile. Or, if it doesn't install many >files, you can just provide a do-install: target in your port Makefile >and install the files yourself. > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42ADC908.6060505>