Date: Wed, 01 Jun 2011 16:57:26 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Christoph Moench-Tegeder <cmt@burggraben.net> Cc: freebsd-ports@FreeBSD.org Subject: Re: lang/guile build fails for me Message-ID: <4DE64546.7070604@FreeBSD.org> In-Reply-To: <20110601131956.GC2223@reindeer.exwg.net> References: <4DE5D8C9.3020506@icyb.net.ua> <4DE6244E.1040301@FreeBSD.org> <20110601114442.GB2223@reindeer.exwg.net> <4DE6392D.5000106@gmx.de> <20110601131956.GC2223@reindeer.exwg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
on 01/06/2011 16:19 Christoph Moench-Tegeder said the following:
> Ah, yes, LDFLAGS. The port's Makefile already has
> LDFLAGS="-L${LOCALBASE}/lib" in $CONFIGURE_ENV, and as guile's configure
BTW, I think that CONFIGURE_ENV in the port's Makefile better be set with +=, for
safety.
> is a standard autoconf configure, $LDFLAGS should be picked up (the
> output of "./configure --help" supports this), but... well, it isn't.
Looks like LDFLAGS are lost from the environment before configure is run:
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value=' -rpath=/usr/lib:/usr/local/lib'
And given the USE_NCURSES workaround posted in this thread, that takes to
Mk/bsd.ncurses.mk where we have:
...
NCURSES_LDFLAGS+= -rpath=${NCURSESRPATH}
.if defined(LDFLAGS)
LDFLAGS+=${NCURSES_LDFLAGS}
.else
LDFLAGS=${NCURSES_LDFLAGS}
.endif
CONFIGURE_ENV+= LDFLAGS="${LDFLAGS}"
...
I think that the above line overrides whatever is set in the port's Makefile.
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DE64546.7070604>