Date: Mon, 13 Jun 2005 13:09:44 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: =?utf-8?B?S8O2dmVzZMOhbiBHw6Fib3I=?= <gabor.kovesdan@t-hosting.hu> Cc: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Makefile question Message-ID: <20050613180944.GB62239@dan.emsphone.com> In-Reply-To: <20050613180721.GA62239@dan.emsphone.com> References: <42ADC155.10304@t-hosting.hu> <20050613174248.GA85674@dan.emsphone.com> <42ADC908.6060505@t-hosting.hu> <20050613180721.GA62239@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jun 13), Dan Nelson said:
> In the last episode (Jun 13):
> > 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.
>
> Yes, that should have worked. Does it do what you want if you manually
> run ./configure --prefix=/usr/local/appname ? If not, then the
> configure script of the Makefile is broken, and you will need to patch
> it or install the files yourself.
Also, if you remove the leading @-sign from line 3293 of
ports/Mk/bsd.port.mk, you can see the exact commandline that the port
Makefile uses when it tries to run the configure script.
--
Dan Nelson
dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050613180944.GB62239>