Date: Thu, 14 Jun 2001 19:58:20 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Jonathan Belson <jonb@innovision-group.com> Cc: freebsd-ports@FreeBSD.org Subject: Re: [Q] ports, configure and environmental variables Message-ID: <20010614195820.B729@ringworld.oblivion.bg> In-Reply-To: <NFBBIJCJGLAFOKNCJHKHIEDDCEAA.jonb@innovision-group.com>; from jonb@innovision-group.com on Thu, Jun 14, 2001 at 01:57:32PM %2B0100 References: <NFBBIJCJGLAFOKNCJHKHIEDDCEAA.jonb@innovision-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 14, 2001 at 01:57:32PM +0100, Jonathan Belson wrote:
> Hiya
>
>
> I've run into a problem with a KDE program for which I'm trying to make
> a port. After running configure and creating the makefiles, it then
> reruns aclocal, automake and autoconf, then reruns the new configure
> script.
>
> Since this time it doesn't have CONFIGURE_ENVs set, the script fails since
> it can't find '-lqt', 'moc' etc. If I define $MOC and $LIBQT from the
> shell before starting the make process, everything works fine.
>
> Is there an approved way to define ENVs in a port? The alternative is
> to patch the projects build scripts, but I'd rather go for the simpler
> approach first.
A simpler approach is to add this line:
MAKE_ENV+= ${CONFIGURE_ENV}
to your port's Makefile :)
G'luck,
Peter
--
What would this sentence be like if it weren't self-referential?
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?20010614195820.B729>