FreeBSD_HEAD-tests - Build #1555 - Failure

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

FreeBSD_HEAD_amd64_gcc4.9 - Build #633 - Fixed

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #633 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/633/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/633/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/633/

FreeBSD_HEAD-tests - Build #1554 - Fixed

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

FreeBSD_HEAD_amd64_gcc4.9 - Build #632 - Failure

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #632 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/632/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/632/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/63

Re: CURRENT: build failure with clang 3.7.0

2015-10-09 Thread Dimitry Andric
On 07 Oct 2015, at 13:33, O. Hartmann wrote: ... > The buildworld error when building with CXXFLAGS+= -std=c++11 is > then > > [...] > cc -O2 -pipe -O3 -O3 -pipe -march=native -I. > -I/usr/obj/usr/src/lib/ncurses/menu/../ncurses > -I/usr/src/lib/ncurses/menu/../ncurses -I/usr/src/

FreeBSD_HEAD_amd64_gcc4.9 - Build #631 - Fixed

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #631 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/631/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/631/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/631/

FreeBSD_HEAD-tests - Build #1553 - Still Unstable

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

Re: The kern.ipc.somaxconn limit revisited.

2015-10-09 Thread Adrian Chadd
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 :) -a On 9 October 2015 at 00:23, White Knight wrote: > Hi, > > Back in 2012, raising the limit of kern.ipc.somaxcann was discussed (now > properly called kern.ipc.acceptqueue) bu

Re: kyua SIGBUS'ing with clang 3.7.0 (was FreeBSD_HEAD-tests - Build #1540 - Unstable)

2015-10-09 Thread Dimitry Andric
On 09 Oct 2015, at 04:29, Craig Rodrigues wrote: > > On Wed, Oct 7, 2015 at 2:28 PM, Dimitry Andric wrote: >> >> Do you still have a copy of the earlier executable? Can you post it >> somewhere? > I was able to reproduce the problem. ... > #0 0x00080085dcfd in std::__1::ios_base::Init::In

FreeBSD_HEAD-tests - Build #1552 - Still unstable

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD-tests - Build #1552 - Still unstable: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1552/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1552/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD-tests/1552/console Change su

FreeBSD_HEAD_amd64_gcc4.9 - Build #630 - Still Failing

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #630 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/630/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/630/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc

FreeBSD_HEAD_amd64_gcc4.9 - Build #629 - Failure

2015-10-09 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc4.9 - Build #629 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/629/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/629/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc4.9/62

FreeBSD_HEAD-tests - Build #1551 - Failure

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

EXTATTR_MAXNAMELEN in

2015-10-09 Thread Milind Changire
Hi, The macro EXTATTR_MAXNAMELEN in has been defined as NAME_MAX ... but the macro definition is only available if _KERNEL has been defined. Shouldn't the macro EXTATTR_MAXNAMELEN be available to user-land code as well? -- Milind ___ freebsd-current@fr

The kern.ipc.somaxconn limit revisited.

2015-10-09 Thread White Knight
Hi, Back in 2012, raising the limit of kern.ipc.somaxcann was discussed (now properly called kern.ipc.acceptqueue) but nothing came of it. The old discussion is here: https://lists.freebsd.org/pipermail/freebsd-current/2012-January/030970.html We are running into problems with the limit