Re: [CFT] Buildworld ccache support

2015-11-10 Thread Juan Ramón Molina Menor
Hi Bryan. Since ccache support was added to base in r290526 I’m not seeing the issues I had previously reported. I have now WITH_CCACHE_BUILD in src.conf and no make.conf and ccache is working as expected. Thank you! Juan ___

Re: [CFT] Buildworld ccache support

2015-10-28 Thread Bryan Drewery
On 10/27/2015 10:27 PM, Simon J. Gerraty wrote: > Bryan Drewery wrote: >> https://people.freebsd.org/~bdrewery/patches/world-ccache.diff > > In the Junos build - where we used ccache for quite some time > I did: > > _CC := ${CC} > CC = ${CCACHE_ENV} ${_CC} > > Since

Re: [CFT] Buildworld ccache support

2015-10-27 Thread Simon J. Gerraty
Bryan Drewery wrote: > https://people.freebsd.org/~bdrewery/patches/world-ccache.diff In the Junos build - where we used ccache for quite some time I did: _CC := ${CC} CC = ${CCACHE_ENV} ${_CC} Since sometimes you want the compiler without ccache - eg when linking. That

Re: [CFT] Buildworld ccache support

2015-10-21 Thread Bryan Drewery
Why not cc me or even send this re: to the original thread? On 10/20/2015 6:32 AM, Juan Ramón Molina Menor wrote: > Hi! > > I’m certainly doing it wrong, because CCACHE does not kick in after > applying the patch and modifying make.conf. CCACHE stats ('ccache -z' > followed by 'ccache -s')

Re: [CFT] Buildworld ccache support

2015-10-21 Thread Juan Ramón Molina Menor
Hi Bryan. Why not cc me or even send this re: to the original thread? I’m not used to mailing lists etiquette, sorry. I thought receiving two copies of the same message would bother you. Now I realize there are digests and maybe other less direct methods for message delivery. Best

Re: [CFT] Buildworld ccache support

2015-10-21 Thread Juan Ramón Molina Menor
Why not cc me or even send this re: to the original thread? On 10/20/2015 6:32 AM, Juan Ramón Molina Menor wrote: Hi! I’m certainly doing it wrong, because CCACHE does not kick in after applying the patch and modifying make.conf. CCACHE stats ('ccache -z' followed by 'ccache -s') remain at

Re: [CFT] Buildworld ccache support

2015-10-21 Thread Bryan Drewery
On 10/21/2015 1:44 PM, Juan Ramón Molina Menor wrote: > +.if ${CC:M/*} == "" > +# Can use PATH. > +PATH:= ${CCACHE_WRAPPER_PATH}:${PATH} These lines in particular did have problems that I fixed recently. - It would potentially add /usr/local/libexec/ccache into PATH multiple times in sub-makes

Re: [CFT] Buildworld ccache support

2015-10-21 Thread Bryan Drewery
On 10/21/2015 3:13 PM, Bryan Drewery wrote: > On 10/21/2015 1:44 PM, Juan Ramón Molina Menor wrote: >> +.if ${CC:M/*} == "" >> +# Can use PATH. >> +PATH:= ${CCACHE_WRAPPER_PATH}:${PATH} > > These lines in particular did have problems that I fixed recently. > > - It would potentially add

Re: [CFT] Buildworld ccache support

2015-10-20 Thread Freddie Cash
On Tue, Oct 20, 2015 at 6:32 AM, Juan Ramón Molina Menor wrote: > Hi! > > I’m certainly doing it wrong, because CCACHE does not kick in after > applying the patch and modifying make.conf. CCACHE stats ('ccache -z' > followed by 'ccache -s') remain at zero during buildworld while

Re: [CFT] Buildworld ccache support

2015-10-20 Thread Juan Ramón Molina Menor
Le 20/10/2015 17:50, Freddie Cash a écrit : On Tue, Oct 20, 2015 at 6:32 AM, Juan Ramón Molina Menor >wrote: Hi! I’m certainly doing it wrong, because CCACHE does not kick in after applying the patch and modifying make.conf. CCACHE stats

Re: [CFT] Buildworld ccache support

2015-10-15 Thread Bryan Drewery
> On Oct 15, 2015, at 17:31, Warren Block wrote: > >> On Thu, 15 Oct 2015, Bryan Drewery wrote: >> >> Hi, >> >> If you are interested in using ccache in buildworld please consider >> using this patch locally and giving me some feedback. The current >> advice for

Re: [CFT] Buildworld ccache support

2015-10-15 Thread Warren Block
On Thu, 15 Oct 2015, Bryan Drewery wrote: Hi, If you are interested in using ccache in buildworld please consider using this patch locally and giving me some feedback. The current advice for ccache+buildworld (the CC:= trick in make.conf) actually results in the build thinking you are using a