On 3/3/2013 7:37 PM, Eitan Adler wrote:
Some time ago (2012-01-21 17:40:15 UTC) I committed a change which
converted all uses of
BUILD_DEPENDS= ${RUN_DEPENDS}
to
BUILD_DEPENDS:= ${RUN_DEPENDS}
Writing:
At the moment 1385 ports use BUILD_DEPENDS= ${RUN_DEPENDS} and 450
ports
On 4 Mar 2013 01:38, Eitan Adler li...@eitanadler.com wrote:
Some time ago (2012-01-21 17:40:15 UTC) I committed a change which
converted all uses of
BUILD_DEPENDS= ${RUN_DEPENDS}
to
BUILD_DEPENDS:= ${RUN_DEPENDS}
Writing:
At the moment 1385 ports use BUILD_DEPENDS=
Eitan Adler li...@eitanadler.com wrote:
Some time ago (2012-01-21 17:40:15 UTC) I committed a change which
converted all uses of
BUILD_DEPENDS= ${RUN_DEPENDS}
to
BUILD_DEPENDS:= ${RUN_DEPENDS}
I don't understand this. RUN_DEPENDS=${BUILD_DEPENDS} is buggy,
because you can end up with
Chris Rees wrote, whilst quoting Eitan Adler:
Ports should *not* assume that BUILD_DEPENDS is clear when initiated
and ports should explicitly duplicate RUN_DEPENDS.
Why not? When is ccache added to BUILD_DEPENDS? I guess I just don't see
how this can happen.
/etc/make.conf can make this
On 4 March 2013 10:50, Chris Rees utis...@gmail.com wrote:
Add WITH_CCACHE_BUILD=yes to /etc/make.conf
Use this Makefile:
Try make run-depends-list with and without the commented line. Note
that USE_CMAKE, USE_GMAKE, etc. can also trigger the buggy behavior.
Note that this behavior is
Some time ago (2012-01-21 17:40:15 UTC) I committed a change which
converted all uses of
BUILD_DEPENDS= ${RUN_DEPENDS}
to
BUILD_DEPENDS:= ${RUN_DEPENDS}
Writing:
At the moment 1385 ports use BUILD_DEPENDS= ${RUN_DEPENDS} and 450
ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch
