On 9/4/2012 11:36 AM, Jeffrey Bouquet wrote: > WITH_CCACHE_BUILD="yes" seems to be working... howsoever a few (2) times > recently, portmaster would complete entirely (signaled by the 'yell' command > as " && yell", but returning to that tty0 (xterm or...) the compiler will be > still working on the already-upgraded port > [1] > (easily stopped by a cntl-c, and that is the whole story) but maybe > portmaster no longer works with all ports with ccache? or some other recent > innovation in the port building system... or the way ccache > works, that it didn't previously, or ?? > > Maybe just trivia, could be a seldom ocurrence ( No time to repeat for now to > check which port that was, etc..). Or maybe if I happen > across an instance where there is more of a scrollback buffer I'd see > the cause right away. > > [1] as if a second command had been scheduled to start when the > first completed... > > J. Bouquet
portmaster already had native ccache support. You do not need to use WITH_CCACHE_BUILD with it. There shouldn't be any adverse affects of setting it though, as both just update the PATH. Bryan _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
