FreeBSD_HEAD-tests - Build #1611 - Unstable

2015-10-21 Thread jenkins-admin
FreeBSD_HEAD-tests - Build #1611 - Unstable: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1611/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1611/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1611/console Change

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')

FreeBSD_HEAD-tests - Build #1612 - Fixed

2015-10-21 Thread jenkins-admin
FreeBSD_HEAD-tests - Build #1612 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1612/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1612/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1612/console Change summaries:

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: is building kernel in /sys/amd64/conf depreciated in 11 ?

2015-10-21 Thread John-Mark Gurney
John wrote this message on Tue, Oct 20, 2015 at 17:40 +0100: > as subject - is building kernel in /sys/amd64/conf depreciated? > > I can get a modified kernel to build and install in /usr/src but not > in /sys/amd64/conf. I always used to be able to do this in there, then > again I either used

Re: The kern.ipc.somaxconn limit revisited.

2015-10-21 Thread White Knight
On 2015-10-13 01:32, White Knight wrote: On 2015-10-10 02:47, Adrian Chadd wrote: I think it's worth upping to an int type, so we can eventually up it to > 64k. Please do submit diffs for revie.w :) I'll work on the patch this week, thank you. I have submitted a bug report, with a patch

Re: is building kernel in /sys/amd64/conf depreciated in 11 ?

2015-10-21 Thread John
On Tue, Oct 20, 2015 at 11:55:04PM -0400, Benjamin Kaduk wrote: Why is your kernel build pulling in bsd.port.mk? Please post src.conf and make.conf. [make.conf] MALLOC_PRODUCTION=yes WITH_CCACHE_BUILD=yes MAKE_JOBS_NUMBER=16 [src.conf] PORTS_MODULES=x11/nvidia-driver This is not exactly

env functionality of config(5) has no effect?

2015-10-21 Thread Eggert, Lars
Hi, I'm trying to include some loader tunables in the kernel, via the "env" functionality described in config(5). When I look at the compiled kernel binary with strings(1), I see that the tunables are compiled in. However, they don't seem to take any effect when booting the kernel, and they