Re: -current build failure after SVN r340130

2018-11-04 Thread Michael Butler
Confirmed to be fixed by SVN r340134 - thanks! On 11/4/18 1:50 PM, Michael Butler wrote: > ===> libexec/dma/dma-mbox-create (all) > Building > /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o > In file included from /usr/src/contrib/dma/dma-mbox-create.c:51: > /usr/obj/us

Re: -current build failure after SVN r340130

2018-11-04 Thread Mariusz Zaborski
On Sun, Nov 04, 2018 at 01:50:31PM -0500, Michael Butler wrote: > ===> libexec/dma/dma-mbox-create (all) > Building > /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o > In file included from /usr/src/contrib/dma/dma-mbox-create.c:51: > /usr/obj/usr/src/amd64.amd64/tmp/usr/

-current build failure after SVN r340130

2018-11-04 Thread Michael Butler
===> libexec/dma/dma-mbox-create (all) Building /usr/obj/usr/src/amd64.amd64/libexec/dma/dma-mbox-create/dma-mbox-create.o In file included from /usr/src/contrib/dma/dma-mbox-create.c:51: /usr/obj/usr/src/amd64.amd64/tmp/usr/include/capsicum_helpers.h:161:1: error: all paths through this function w

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 with some AVX-equipted > >> Intel processors gets fixed soon? > > >

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 upstream, did number of bisections to drill down t

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 found an LLVM committer who h

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 -pipe -march=native -I. > > -I/usr/obj/usr/src

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/

Re: CURRENT: build failure with clang 3.7.0

2015-10-07 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: > > > > On Wed, 7 Oct 2015 13:23:48 +0200

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: > > > > > > > On 07 Oct 2015, at 09:37,

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 wrote: > > > > > > > > I hit on a box this nasty/sticky error w

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 buildworld. > > > > > > /usr/src is on r288980 > > ...

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 --- > ... > > -c > > /usr/src/usr.sbin/wpa/wpa_sup

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 > /usr/src/usr.sbin/wpa/wpa_supplicant/../../../contrib/wpa//src/common/ieee802_11_common.c > -o ieee802_11_c

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 system, not things in your so

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 delete-

Re: CURRENT BUILD FAILURE sys/modules/cxgbe

2013-10-07 Thread Dimitry Andric
On Oct 7, 2013, at 23:04, Outback Dingo wrote: > On Mon, Oct 7, 2013 at 5:00 PM, Ian Lepore wrote: > >> On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: >>> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE >> -nostdinc >>> -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../de

Re: CURRENT BUILD FAILURE sys/modules/cxgbe

2013-10-07 Thread Outback Dingo
On Mon, Oct 7, 2013 at 5:00 PM, Ian Lepore wrote: > On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: > > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE > -nostdinc > > -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe > > -DHAVE_KERNEL_OPTION_HEADERS -include > >

Re: CURRENT BUILD FAILURE sys/modules/cxgbe

2013-10-07 Thread Ian Lepore
On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote: > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/a

CURRENT BUILD FAILURE sys/modules/cxgbe

2013-10-07 Thread Outback Dingo
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-

r241879 -current build failure in lib/libwrap

2012-10-22 Thread Kim Culhan
Output of buildworld: http://pastebin.com/z0r03QpZ thanks -kim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: -current build failure

2012-07-25 Thread Konstantin Belousov
On Wed, Jul 25, 2012 at 09:03:58AM +0100, David Chisnall wrote: > On 24 Jul 2012, at 23:43, Konstantin Belousov wrote: > > > As kan rightfully notes, the assumption that &%fs:0 == *%fs:0 holds for > > userspace on amd64, and the same is true for %gs userspace on i386. > > The change you committed

Re: -current build failure

2012-07-25 Thread David Chisnall
On 24 Jul 2012, at 23:43, Konstantin Belousov wrote: > As kan rightfully notes, the assumption that &%fs:0 == *%fs:0 holds for > userspace on amd64, and the same is true for %gs userspace on i386. > The change you committed to clang/llvm/whatever it called just breaks > useful optimization for Fre

Re: -current build failure

2012-07-24 Thread Konstantin Belousov
On Tue, Jul 24, 2012 at 10:08:13PM +0100, David Chisnall wrote: > On 23 Jul 2012, at 20:53, David Chisnall wrote: > > > On 23 Jul 2012, at 20:18, Konstantin Belousov wrote: > > > >> Longer description is that pc_curthread is offset 0 if %gs-based. > >> The dereferenced pointer point to the struct

Re: -current build failure

2012-07-24 Thread David Chisnall
On 23 Jul 2012, at 20:53, David Chisnall wrote: > On 23 Jul 2012, at 20:18, Konstantin Belousov wrote: > >> Longer description is that pc_curthread is offset 0 if %gs-based. >> The dereferenced pointer point to the struct thread, which contains >> td_proc pointer at offset 8. Instead, clang seems

Re: -current build failure

2012-07-23 Thread David Chisnall
On 23 Jul 2012, at 20:18, Konstantin Belousov wrote: > Longer description is that pc_curthread is offset 0 if %gs-based. > The dereferenced pointer point to the struct thread, which contains > td_proc pointer at offset 8. Instead, clang seems to dereference > td_proc from offset 8 based on %gs, or

Re: -current build failure

2012-07-23 Thread Konstantin Belousov
On Sun, Jul 22, 2012 at 09:01:19PM +0300, Konstantin Belousov wrote: > [Why don't you bother to configure your mail client properly ? > Answering to email with 500+ long lines is not trivial] > > On Sun, Jul 22, 2012 at 06:18:12PM +0100, David Chisnall wrote: > > > > On 21 Jul 2012, at 22:16, Kon

Re: -current build failure

2012-07-22 Thread Konstantin Belousov
[Why don't you bother to configure your mail client properly ? Answering to email with 500+ long lines is not trivial] On Sun, Jul 22, 2012 at 06:18:12PM +0100, David Chisnall wrote: > > On 21 Jul 2012, at 22:16, Konstantin Belousov wrote: > > > On Sat, Jul 21, 2012 at 04:00:45PM -0400, Kim Culh

Re: -current build failure

2012-07-22 Thread David Chisnall
On 21 Jul 2012, at 22:16, Konstantin Belousov wrote: > On Sat, Jul 21, 2012 at 04:00:45PM -0400, Kim Culhan wrote: >> On Fri, Jul 20, 2012 at 11:40 AM, Dimitry Andric wrote: >>> On 2012-07-20 16:49, Kim Culhan wrote: Seeing this for r:238655 >>> ... In file included from /usr/src

Re: -current build failure

2012-07-21 Thread Kim Culhan
On Sat, Jul 21, 2012 at 5:16 PM, Konstantin Belousov wrote: > On Sat, Jul 21, 2012 at 04:00:45PM -0400, Kim Culhan wrote: >> On Fri, Jul 20, 2012 at 11:40 AM, Dimitry Andric wrote: >> > On 2012-07-20 16:49, Kim Culhan wrote: >> >> Seeing this for r:238655 >> > ... >> >> In file included from >>

Re: -current build failure

2012-07-21 Thread Konstantin Belousov
On Sat, Jul 21, 2012 at 04:00:45PM -0400, Kim Culhan wrote: > On Fri, Jul 20, 2012 at 11:40 AM, Dimitry Andric wrote: > > On 2012-07-20 16:49, Kim Culhan wrote: > >> Seeing this for r:238655 > > ... > >> In file included from > >> /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: > >> .

Re: -current build failure

2012-07-21 Thread Kim Culhan
On Fri, Jul 20, 2012 at 11:40 AM, Dimitry Andric wrote: > On 2012-07-20 16:49, Kim Culhan wrote: >> Seeing this for r:238655 > ... >> In file included from >> /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: >> ./machine/pcpu.h:226:13: error: indirection of non-volatile null >> pointer

Re: -current build failure

2012-07-21 Thread Konstantin Belousov
On Sat, Jul 21, 2012 at 12:59:07PM +0100, David Chisnall wrote: > On 21 Jul 2012, at 00:16, Konstantin Belousov wrote: > > > Ok, I stand corrected. But the standard does not say what you claim > > either. It only specifies that NULL pointer is unequal to any pointer > > to object or function (impl

Re: -current build failure

2012-07-21 Thread David Chisnall
On 21 Jul 2012, at 00:16, Konstantin Belousov wrote: > Ok, I stand corrected. But the standard does not say what you claim > either. It only specifies that NULL pointer is unequal to any pointer > to object or function (implicitely saying that you can create a C object > or function pointer to whi

Re: -current build failure

2012-07-21 Thread Konstantin Belousov
On Sat, Jul 21, 2012 at 02:43:16PM +0300, Konstantin Belousov wrote: > On Sat, Jul 21, 2012 at 01:35:26PM +0200, Dimitry Andric wrote: > > On 2012-07-21 01:16, Konstantin Belousov wrote: > > > On Fri, Jul 20, 2012 at 10:07:05PM +0100, David Chisnall wrote: > > >> On 20 Jul 2012, at 17:33, Konstanti

Re: -current build failure

2012-07-21 Thread Konstantin Belousov
On Sat, Jul 21, 2012 at 01:35:26PM +0200, Dimitry Andric wrote: > On 2012-07-21 01:16, Konstantin Belousov wrote: > > On Fri, Jul 20, 2012 at 10:07:05PM +0100, David Chisnall wrote: > >> On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: > >> > >>> It is not related to dtrace at all, and indeed O

Re: -current build failure

2012-07-21 Thread Dimitry Andric
On 2012-07-21 01:16, Konstantin Belousov wrote: > On Fri, Jul 20, 2012 at 10:07:05PM +0100, David Chisnall wrote: >> On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: >> >>> It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. >>> This is a bug in clang, we compile our kernel

Re: -current build failure

2012-07-20 Thread Konstantin Belousov
On Fri, Jul 20, 2012 at 10:07:05PM +0100, David Chisnall wrote: > On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: > > > It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. > > This is a bug in clang, we compile our kernel in freestanding environment. > > The copies of the

Re: -current build failure

2012-07-20 Thread David Chisnall
On 20 Jul 2012, at 17:33, Konstantin Belousov wrote: > It is not related to dtrace at all, and indeed OFFSETOF_CURTHREAD is 0. > This is a bug in clang, we compile our kernel in freestanding environment. The copies of the C spec that I have do not differentiate between freestanding and hosted en

Re: -current build failure

2012-07-20 Thread Konstantin Belousov
On Fri, Jul 20, 2012 at 05:40:32PM +0200, Dimitry Andric wrote: > On 2012-07-20 16:49, Kim Culhan wrote: > > Seeing this for r:238655 > ... > > In file included from > > /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: > > ./machine/pcpu.h:226:13: error: indirection of non-volatile null

Re: -current build failure

2012-07-20 Thread Dimitry Andric
On 2012-07-20 16:49, Kim Culhan wrote: > Seeing this for r:238655 ... > In file included from > /usr/src/sys/modules/dtrace/dtrace/../../../sys/pcpu.h:44: > ./machine/pcpu.h:226:13: error: indirection of non-volatile null > pointer will be deleted, not trap > [-Werror,-Wnull-dereference] >

-current build failure

2012-07-20 Thread Kim Culhan
Seeing this for r:238655 ===> dtrace/dtrace (depend) @ -> /usr/src/sys machine -> /usr/src/sys/amd64/include x86 -> /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Kris Kennaway
On Mon, Nov 18, 2002 at 06:15:24PM -0500, Garrett Wollman wrote: > < said: > > > It's described in the file itself. Can you please file a PR about the > > missing manpage documentation? > > make.conf is no longer installed in -current. A user trying to > understand why some glop is being added

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Garrett Wollman
< said: > It's described in the file itself. Can you please file a PR about the > missing manpage documentation? make.conf is no longer installed in -current. A user trying to understand why some glop is being added automatically to CFLAGS will probably not think to read /usr/share/examples/etc

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Kris Kennaway
On Mon, Nov 18, 2002 at 08:57:24PM +0100, Joerg Wunsch wrote: > As Kris Kennaway wrote: > > > > What am i supposed to do in order to get cross-compilation working > > > properly? > > > > NO_CPU_CFLAGS=yes > > > > This is documented in make.conf. > > At least not in my version of make.conf's man

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Joerg Wunsch
As Kris Kennaway wrote: > > What am i supposed to do in order to get cross-compilation working > > properly? > > NO_CPU_CFLAGS=yes > > This is documented in make.conf. At least not in my version of make.conf's man page. Just checked, neither in the current version. I (and obviously not only I

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Kris Kennaway
On Mon, Nov 18, 2002 at 02:14:58PM +0100, Joerg Wunsch wrote: > What am i supposed to do in order to get cross-compilation working > properly? I've already tried a number of things, and my -current > from August at least gave in when setting MACHINE_ARCH=avr for > the cross-coimpilation. Previou

Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Joerg Wunsch
As Matthew N. Dodd wrote: > > I really /hate/ this CPU feature crap. > > So do I. > > I've also found that the only way to reliablly disable it is to comment it > out from sys.mk. Maybe i should do this using a preconfigure script in my port... >:-) -- cheers, J"org .-.-. --..

CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain])

2002-11-18 Thread Joerg Wunsch
- Forwarded message from Kris Kennaway <[EMAIL PROTECTED]> - One or more ports that you maintain are currently unbuildable under FreeBSD 5.0-CURRENT/i386 on the FreeBSD package-building cluster. [...] - End forwarded message - ... gmake[2]: Entering directory `/tmp/a/ports/devel