Re: Fixed with r289221 (was: Re: CURRENT: build failure with clang 3.7.0)

2015-10-15 Thread O. Hartmann
On Tue, 13 Oct 2015 18:30:08 +0200 Dimitry Andric wrote: > On 10 Oct 2015, at 19:39, Dimitry Andric wrote: > > > > On 10 Oct 2015, at 18:12, O. Hartmann wrote: > > ... > >> Is there any chance that the failure of clang 3.7.0

Fixed with r289221 (was: Re: CURRENT: build failure with clang 3.7.0)

2015-10-13 Thread Dimitry Andric
On 10 Oct 2015, at 19:39, Dimitry Andric wrote: > > On 10 Oct 2015, at 18:12, O. Hartmann wrote: > ... >> Is there any chance that the failure of clang 3.7.0 with some AVX-equipted >> Intel >> processors gets fixed soon? > > I reported the bug

Re: CURRENT: build failure with clang 3.7.0

2015-10-10 Thread O. Hartmann
Am Fri, 9 Oct 2015 23:07:18 +0200 Dimitry Andric schrieb: > 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

Re: CURRENT: build failure with clang 3.7.0

2015-10-10 Thread Dimitry Andric
On 10 Oct 2015, at 18:12, O. Hartmann wrote: ... > Is there any chance that the failure of clang 3.7.0 with some AVX-equipted > Intel > processors gets fixed soon? I reported the bug upstream, did number of bisections to drill down to the root cause (hopefully), and

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 >

Re: CURRENT: build failure with clang 3.7.0

2015-10-08 Thread O. Hartmann
On Wed, 07 Oct 2015 13:50:54 -0700 John Baldwin wrote: > On Wednesday, October 07, 2015 09:09:50 PM O. Hartmann wrote: > > Am Wed, 07 Oct 2015 11:03 -0700 > > John Baldwin schrieb: > > > > > On Wednesday, October 07, 2015 01:33:23 PM O. Hartmann wrote: > > >

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread John Baldwin
On Wednesday, October 07, 2015 09:09:50 PM O. Hartmann wrote: > Am Wed, 07 Oct 2015 11:03 -0700 > John Baldwin schrieb: > > > On Wednesday, October 07, 2015 01:33:23 PM O. Hartmann wrote: > > > On Wed, 7 Oct 2015 13:23:48 +0200 > > > Dimitry Andric wrote: > >

CURRENT: build failure with clang 3.7.0

2015-10-07 Thread O. Hartmann
I hit on a box this nasty/sticky error when performing buildworld. /usr/src is on r288980 svn status gives #: [src] svn st ? .snap ? .sujournal ? etc/rc.d/tests ? sys/amd64/conf/HAGENVONTRONJE By the way, it seems that etc/rc.d/tests doesn't get deleted via "make

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread NGie Cooper
> On Oct 7, 2015, at 00:37, O. Hartmann wrote: > > I hit on a box this nasty/sticky error when performing buildworld. … > By the way, it seems that etc/rc.d/tests doesn't get deleted via "make > delete-old”. make delete-old only cleans up things installed to the

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread O. Hartmann
Am Wed, 07 Oct 2015 11:03 -0700 John Baldwin schrieb: > On Wednesday, October 07, 2015 01:33:23 PM O. Hartmann wrote: > > On Wed, 7 Oct 2015 13:23:48 +0200 > > Dimitry Andric wrote: > > > > > On 07 Oct 2015, at 09:37, O. Hartmann

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread O. Hartmann
On Wed, 7 Oct 2015 13:23:48 +0200 Dimitry Andric wrote: > On 07 Oct 2015, at 09:37, O. Hartmann wrote: > > > > I hit on a box this nasty/sticky error when performing buildworld. > > > > /usr/src is on r288980 > ... > > --- ieee802_11_common.o ---

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread Dimitry Andric
On 07 Oct 2015, at 09:37, O. Hartmann wrote: > > I hit on a box this nasty/sticky error when performing buildworld. > > /usr/src is on r288980 ... > --- ieee802_11_common.o --- ... > -c >

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 Thread John Baldwin
On Wednesday, October 07, 2015 01:33:23 PM O. Hartmann wrote: > On Wed, 7 Oct 2015 13:23:48 +0200 > Dimitry Andric wrote: > > > On 07 Oct 2015, at 09:37, O. Hartmann wrote: > > > > > > I hit on a box this nasty/sticky error when performing