Date: Mon, 13 Jun 2005 13:58:30 -0400 From: Johnny Lam <jlam@NetBSD.org> To: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu> Cc: freebsd-ports@freebsd.org Subject: Re: Makefile question Message-ID: <42ADC946.1090304@NetBSD.org> In-Reply-To: <42ADC155.10304@t-hosting.hu> References: <42ADC155.10304@t-hosting.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
Kövesdán Gábor wrote:
>
> I'm trying to make a new port, but the software I'm porting has an
> awkward configure script, and when I run ./configure --prefix=/usr/local
> then every file goes to directly to /usr/local not to /usr/local/bin,
> /usr/local/etc, ...
> Thus I would like to install it into /usr/local/appname.
> I wrote to my Makefile:
>
> GNU_CONFIGURE= YES
> CONFIGURE_ARGS= --prefix=${PREFIX}/appname
>
> But the situation is the same. Everything goes directly to /usr/local,
> as if I wrote just --prefix=${PREFIX}.
Line 2624 of ports/Mk/bsd.ports.mk always adds --prefix=${PREFIX} to
CONFIGURE_ARGS, and I think GNU configure scripts have the last option
taking precedence, meaning it overrides whatever you're setting in the
port Makefile. I don't know what the right thing to do is. Maybe you
can add your special CONFIGURE_ARGS setting after bsd.ports.mk is
included? In NetBSD pkgsrc, we created a new variable to solve this
problem -- GNU_CONFIGURE_PREFIX which defaults to ${PREFIX}, but can be
set to something else by the user.
Cheers,
-- Johnny Lam <jlam@NetBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42ADC946.1090304>