Date: Sat, 25 May 2013 02:48:02 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r318993 - in head: archivers/libcabinet archivers/libcabinet/files devel/libpdel devel/libxalloc finance/libstocks games/libshhcards games/libshhcards/files japanese/ming math/linpack w... Message-ID: <20130525024802.GD89166@FreeBSD.org> In-Reply-To: <201305241635.r4OGZVa7094499@svn.freebsd.org> References: <201305241635.r4OGZVa7094499@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 24, 2013 at 04:35:31PM +0000, Baptiste Daroussin wrote: > New Revision: 318993 > URL: http://svnweb.freebsd.org/changeset/ports/318993 > > Log: > Do not let system make.conf inpact the port's makefile > This fixes build on current > > @@ -13,6 +13,7 @@ USE_LDCONFIG= yes > > SRCFILE= ${WRKSRC}/listcab.cpp > PROGFILE= ${SRCFILE:S/.cpp$//} > +MAKE_ENV= WITHOUT_PROFILE=yes __MAKE_CONF=/dev/null SRCCONF=/dev/null This looks bogus. Can you shed some light on what exactly breaks these ports? Can they be fixed without introducing cryptic constructs in their ports Makefiles? I'd volunteer to fix (when -current gets stable enough to be feasible for remote upgrade; I don't want to get unbootable box). ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130525024802.GD89166>