Re: make buildworld failure on arm64 on -current n267777

On Fri, 26 Jan 2024, at 00:14, void wrote: > In /usr/src # git rev-list --count --first-parent HEAD > 26 in /usr/src, a 'git reset --hard' followed by 'git pull' and then 'git checkout main' fixed this. For some reason, 'git pull --ff-only' didn't pull /usr/src/sys/contrib/dev/acpica/include

make buildworld failure on arm64 on -current n267777

In /usr/src # git rev-list --count --first-parent HEAD 26 include/machine -> /usr/src/sys/arm64/include Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/vers.c Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/8x16.c Building /usr/obj/usr/src/arm64.aarch64/stand/efi/l

Re: f190c36b5d45 buildworld failure: ld: error: undefined symbol: SSL_get_peer_certificate

13 1 0 X 1710 1 0 # Stop 1687753166.044683 # Bye bye I removed /usr/obj/usr/src/amd64.amd64 (or maybe, more bluntly, the contents of /usr/obj/). Updated src to f81be7a8318b, built world OK. I encountered another buildworld failure on a different computer with slightly more recent src. I didn't stop to take details but similarly, build succeeded after I removed /usr/obj/usr/src/amd64.amd64

f190c36b5d45 buildworld failure: ld: error: undefined symbol: SSL_get_peer_certificate

On 25/06/2023 20:57, Graham Perrin wrote: From : clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [dma.full] Error code 1 make[5]: stopped in /usr/src/libexec/dma/dmagent .ERROR_TARGET='dma.full' .ERROR_META_FILE='/usr/o

f190c36b5d45 buildworld failure

From : clang: error: linker command failed with exit code 1 (use -v to see invocation) *** [dma.full] Error code 1 make[5]: stopped in /usr/src/libexec/dma/dmagent .ERROR_TARGET='dma.full' .ERROR_META_FILE='/usr/obj/usr/src/amd64.amd64/libexec/dma/dmagent/

Re: Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Resolved by 76fa62b5232e67ef10476cf1329aaceb9cbc2ff5; ref. https://cgit.freebsd.org/src/commit/?id=76fa62b5232e67ef10476cf1329aaceb9cbc2ff5 Peace, david -- David H. Wolfskill da...@catwhisker.org Putin claimed he wanted to avoid expansion of NATO. See how well THAT

Buildworld failure at main-n261978-44312c28fe2d in /usr/src/usr.sbin/bhyve

Running: freebeast(14.0-C)[4] uname -aUK FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #328 main-n261961-7ae0972c7b8c: Mon Apr 3 11:41:40 UTC 2023 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 1400085 1400085 in meta mode after upd

Re: buildworld failure

> > Also, the buildworld command most likely to build the most amd64 components > > from scratch? > > > seems "make hier" fixed it partially > then WITHOUT_OFED=yes in src.conf. maybe fixed, maybe not. Not fixed. question 1. While building, it fails in some subtr

Re: buildworld failure

On Sat, 18 Feb 2023 00:33:11 -0800 (PST), "Jeffrey Bouquet" wrote: > Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.c > Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.o > sys_bitcount.c:1:10: fatal error: 'sys/bitcount.h' file not fo

Re: buildworld failure

On Sat, Feb 18, 2023 at 12:33:11AM -0800, Jeffrey Bouquet wrote: > Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.c > Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.o > sys_bitcount.c:1:10: fatal error: 'sys/bitcount.h' file not found > #i

buildworld failure

Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.c Building /usr/obj/usr/src/amd64.amd64/tools/build/test-includes/sys_bitcount.o sys_bitcount.c:1:10: fatal error: 'sys/bitcount.h' file not found #include ^~~~ 1 error generated. *** Error code 1 St

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

In my testing 338129 fixed the issue. Seems like the problem is that bsd.crunchgen.mk iterates over all directories to do a make obj when it does the bootstrap-tools phase. On Tue, 21 Aug 2018 at 14:49, Warner Losh wrote: > > > > On Tue, Aug 21, 2018 at 12:38 AM, John Baldwin wrote: >> >> On 8/20

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

I think relaxing the check to just avoid includes of "${SRCTOP}/sys" is probably the best solution. It would be nice to also handle the ${.CURDIR}/../../sys case but since it's just there to prevent ABI issues that's probably fine. Alex On Tue, 21 Aug 2018 at 15:19 Warner Losh wrote: > On Tue,

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

On Tue, Aug 21, 2018 at 8:16 AM, Warner Losh wrote: > There's a half a dozen special targets, however. clean comes to mind... > > > However, this test is needlessly restrictive: > > .if !empty(CFLAGS:M*${SRCTOP}/sys*:N*${SRCTOP}/sys/cddl/compat*: > N*${SRCTOP}/sys/crypto*) > > since it matches >

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

There's a half a dozen special targets, however. clean comes to mind... However, this test is needlessly restrictive: .if !empty(CFLAGS:M*${SRCTOP}/sys*:N*${SRCTOP}/sys/cddl/compat*:N*${SRCTOP}/sys/crypto*) since it matches CFLAGS+=-I${SRCTOP}/sys/sys/disk which is totally legit. It's designe

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

On Tue, Aug 21, 2018 at 7:49 AM, Warner Losh wrote: > > > On Tue, Aug 21, 2018 at 12:38 AM, John Baldwin wrote: > >> On 8/20/18 9:00 PM, O. Hartmann wrote: >> > -BEGIN PGP SIGNED MESSAGE- >> > Hash: SHA512 >> > >> > Am Mon, 20 Aug 2018 21:24:21 +0200 >> > "O. Hartmann" schrieb: >> > >>

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

On Tue, Aug 21, 2018 at 12:38 AM, John Baldwin wrote: > On 8/20/18 9:00 PM, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Mon, 20 Aug 2018 21:24:21 +0200 > > "O. Hartmann" schrieb: > > > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA512 > >> > >> Bui

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

On 8/20/18 9:00 PM, O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Mon, 20 Aug 2018 21:24:21 +0200 > "O. Hartmann" schrieb: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Building NanoBSD world on CURRENT r338113 fails due to: >> >> [...] >> cd /pool

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mon, 20 Aug 2018 21:24:21 +0200 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Building NanoBSD world on CURRENT r338113 fails due to: > > [...] > cd /pool/sources/CURRENT/src/rescue/rescue/../../sbin/gbde && M

buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Building NanoBSD world on CURRENT r338113 fails due to: [...] cd /pool/sources/CURRENT/src/rescue/rescue/../../sbin/gbde && MK_TESTS=no UPDATE_DEPENDFILE=no _RECURSING_CRUNCH=1 MAKEOBJDIRPREFIX=/pool/nanobsd/amd64/ALERICH_amd64/pool/sources/CURREN

Re: Buildworld failure in sys/boot/efi/loader/main.c if WITHOUT_ZFS is defined

Got it fixed in: r323428 | tsoome | 2017-09-11 10:38:53 +0300 (E, 11 sept 2017) | 7 lines r323389 breaks the kernel build when WITHOUT_ZFS is defined in src.conf Need to add #ifdef EFI_ZFS_BOOT guard into efi/loader/main.c PR: 15 Reported by:Sylvain Garrigues sorry about i

Buildworld failure in sys/boot/efi/loader/main.c if WITHOUT_ZFS is defined

===> sys/boot/efi/loader (all) cc -target x86_64-unknown-freebsd12.0 -- sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem - I/usr/src/sys/boot/efi/loader/../../../../lib/libstand -fPIC - DTERM_EMU -I/usr/src/sys/boot/efi/loader - I/usr/src/sys/boot/efi/loader/a

Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

Am Tue, 22 Aug 2017 12:56:22 +0200 Dimitry Andric schrieb: > On 22 Aug 2017, at 06:20, O. Hartmann wrote: > > > > On Mon, 21 Aug 2017 23:47:54 +0200 > > Dimitry Andric wrote: > > > >> On 21 Aug 2017, at 20:52, O. Hartmann wrote: > >>> > >>> I just updated to r322769 and now I face this

Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

On 22 Aug 2017, at 06:20, O. Hartmann wrote: > > On Mon, 21 Aug 2017 23:47:54 +0200 > Dimitry Andric wrote: > >> On 21 Aug 2017, at 20:52, O. Hartmann wrote: >>> >>> I just updated to r322769 and now I face this when trying to recompile >>> kernel/world again: >>> >>> make: "/usr/src/share/m

Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

On Mon, 21 Aug 2017 23:47:54 +0200 Dimitry Andric wrote: > On 21 Aug 2017, at 20:52, O. Hartmann wrote: > > > > I just updated to r322769 and now I face this when trying to recompile > > kernel/world again: > > > > make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version > >

Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

On 21 Aug 2017, at 20:52, O. Hartmann wrote: > > I just updated to r322769 and now I face this when trying to recompile > kernel/world again: > > make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || > echo 0.0.0" > exited on a signal make: "/usr/src/share/mk/bsd.compil

Re: r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

O. Hartmann wrote: > I just updated to r322769 and now I face this when trying to recompile > kernel/world again: > > make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || > echo 0.0.0" > exited on a signal make: "/usr/src/share/mk/bsd.compiler.mk" line 155: Unable >

r322769: make buildkernel/buildworld failure: Unable to determine compiler type for CC=cc

I just updated to r322769 and now I face this when trying to recompile kernel/world again: make: "/usr/src/share/mk/bsd.compiler.mk" line 142: warning: "cc --version || echo 0.0.0" exited on a signal make: "/usr/src/share/mk/bsd.compiler.mk" line 155: Unable to determine compiler type for CC=cc

Re: r311674: buildworld failure: iso_rrip.h:64:2: error: unknown type name 'cd_ino_t'

Please try r311675. Thanks, Conrad On Sun, Jan 8, 2017 at 1:05 AM, O. Hartmann wrote: > It seems, the most recent CURRENT sources are broken (r311674), buildworld > failure occur > at: > > [...] > --- cd9660.o --- > In file included from /usr/src/usr.sbin/makefs/cd

r311674: buildworld failure: iso_rrip.h:64:2: error: unknown type name 'cd_ino_t'

It seems, the most recent CURRENT sources are broken (r311674), buildworld failure occur at: [...] --- cd9660.o --- In file included from /usr/src/usr.sbin/makefs/cd9660.c:108: In file included from /usr/src/usr.sbin/makefs/cd9660.h:57: /usr/src/sys/fs/cd9660/iso_rrip.h:64:2: error: unknown

Re: 'make buildworld' failure

On Thursday 05 January 2017 12:26:58 Hiroki Sato wrote: > hiren panchasara wrote > in <20170104180954.gv17...@strugglingcoder.info>: > > hi> + hrs@ > hi> On 01/04/17 at 12:43P, Oleg V. Nauman wrote: > hi> > ===> usr.sbin/inetd (all) [skip] > hi> > 4 errors generated. > hi> > *** Error code 1 >

Re: 'make buildworld' failure

hiren panchasara wrote in <20170104180954.gv17...@strugglingcoder.info>: hi> + hrs@ hi> On 01/04/17 at 12:43P, Oleg V. Nauman wrote: hi> > ===> usr.sbin/inetd (all) hi> > cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - hi> > B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march

Re: 'make buildworld' failure

+ hrs@ On 01/04/17 at 12:43P, Oleg V. Nauman wrote: > ===> usr.sbin/inetd (all) > cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - > B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem -DLOGIN_CAP -DIPSEC - > g -MD -MF.depend.inetd.o -MTinetd.o -std=gnu99 -fstack-protect

'make buildworld' failure

===> usr.sbin/inetd (all) cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp - B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -march=nehalem -DLOGIN_CAP -DIPSEC - g -MD -MF.depend.inetd.o -MTinetd.o -std=gnu99 -fstack-protector-strong - Wsystem-headers -Werror -Wall -Wno-format-y2k -W

Re: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

> On 30. dets 2016, at 21:40, Toomas Soome wrote: > > >> On 30. dets 2016, at 21:35, Dimitry Andric wrote: >> >> On 30 Dec 2016, at 20:23, O. Hartmann wrote: >>> >>> Recent update of CURRENT to 2310850 fails with buildworld error: >>> >>> [...] >>> ===> lib/atf/libatf-c++ (all) >>> --- all

Re: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

Am Fri, 30 Dec 2016 21:40:27 +0200 Toomas Soome schrieb: > > On 30. dets 2016, at 21:35, Dimitry Andric wrote: > > > > On 30 Dec 2016, at 20:23, O. Hartmann wrote: > >> > >> Recent update of CURRENT to 2310850 fails with buildworld error: > >> > >> [...] > >> ===> lib/atf/libatf-c++ (all

Re: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

> On 30. dets 2016, at 21:35, Dimitry Andric wrote: > > On 30 Dec 2016, at 20:23, O. Hartmann wrote: >> >> Recent update of CURRENT to 2310850 fails with buildworld error: >> >> [...] >> ===> lib/atf/libatf-c++ (all) >> --- all_subdir_lib/libstand --- >> --- nandfs.o --- >> /usr/src/lib/libst

Re: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

On 30 Dec 2016, at 20:23, O. Hartmann wrote: > > Recent update of CURRENT to 2310850 fails with buildworld error: > > [...] > ===> lib/atf/libatf-c++ (all) > --- all_subdir_lib/libstand --- > --- nandfs.o --- > /usr/src/lib/libstand/nandfs.c:1049:15: error: too many arguments to function > call

r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

Recent update of CURRENT to 2310850 fails with buildworld error: [...] ===> lib/atf/libatf-c++ (all) --- all_subdir_lib/libstand --- --- nandfs.o --- /usr/src/lib/libstand/nandfs.c:1049:15: error: too many arguments to function call, expected 6, have 7 buffer, NULL); ^

CURRENT: arm64 buildworld failure: numa_setaffinity.pico: In function `numa_setaffinity':

Trying to build AARCH64 world on amd64 box running most recent CURRENT (FreeBSD 12.0-CURRENT #23 r310556: Sun Dec 25 21:45:35 CET 2016 amd64), sources are r310603. port devel/aarch64-binutils is installed as requested, the environment has been setup using setenv MAKEOBJDIRPREFIX /pool/sources/C

Re: r 307698: buildworld failure: tconfig.h:6:10: fatal error: 'auto-host.h' file not found

> On Oct 20, 2016, at 21:39, O. Hartmann wrote: > > Recent r307698 is preventued from beeing built by a compiler error, see below. > > I also face a problem with the subversion tree a couple of day right now: > > # svn update > Updating '.': > Restored 'tests/sys/geom/class/uzip/1_endian_littl

r 307698: buildworld failure: tconfig.h:6:10: fatal error: 'auto-host.h' file not found

Recent r307698 is preventued from beeing built by a compiler error, see below. I also face a problem with the subversion tree a couple of day right now: # svn update Updating '.': Restored 'tests/sys/geom/class/uzip/1_endian_little.img.uzip.uue' At revision 307698. This 'restored' message occur

Re: FreeBSD 11.0 i386 buildworld failure

On Monday, October 03, 2016 10:47:26 PM Robert_Burmeister wrote: > Robert_Burmeister wrote > > FreeBSD 11.0 i386 Stable > > > > I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September > > 2016. > > Upon refreshing and rebuilding world to catch the 28 September 2016 > > Release upd

Re: FreeBSD 11.0 i386 buildworld failure

24.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134583.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsub

Re: FreeBSD 11.0 i386 buildworld failure

this message in context: http://freebsd.1045724.x6.nabble.com/FreeBSD-11-0-i386-buildworld-failure-tp6133823p6134033.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list https://lists.freeb

FreeBSD 11.0 i386 buildworld failure

FreeBSD 11.0 i386 Stable I successfully upgraded from FreeBSD 10.3 to 11.0 Stable on 23 September 2016. Upon refreshing and rebuilding world to catch the 28 September 2016 Release update, buildworld failed using the same build options that had worked for the 22 Sept code. Tail: --- all_subdir_

make buildworld failure?

Hi, yes, I do have -DNO_CLEAN in my make command, which gives: make -DNO_CLEAN buildworld ===> secure/libexec/sftp-server (all) /usr/local/libexec/ccache/world/cc -target x86_64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin -O2 -pipe -I/usr/src/secure/libexec/

Re: CURRENT: buildworld failure due to nvmecontrol source error

> On Jan 30, 2016, at 04:10, Outback Dingo wrote: > > On Sat, Jan 30, 2016 at 12:39 PM, O. Hartmann > wrote: > >> Buildworld (r295070) fails in building nvmecontrol patches correctly: >> >> [...] >> (cd /usr/src/lib/libc/tests/gen && DEPENDFILE=.depend.raise_test >> NO_SUBDIR=1 make >> -f /u

Re: CURRENT: buildworld failure due to nvmecontrol source error

On Sat, Jan 30, 2016 at 12:39 PM, O. Hartmann wrote: > Buildworld (r295070) fails in building nvmecontrol patches correctly: > > [...] > (cd /usr/src/lib/libc/tests/gen && DEPENDFILE=.depend.raise_test > NO_SUBDIR=1 make > -f /usr/src/lib/libc/tests/gen/Makefile _RECURSING_PROGS=t > PROG=raise_t

CURRENT: buildworld failure due to nvmecontrol source error

Buildworld (r295070) fails in building nvmecontrol patches correctly: [...] (cd /usr/src/lib/libc/tests/gen && DEPENDFILE=.depend.raise_test NO_SUBDIR=1 make -f /usr/src/lib/libc/tests/gen/Makefile _RECURSING_PROGS=t PROG=raise_test ) --- all_subdir_share --- ===> share/i18n/csmapper/APPLE (a

Re: r 291486: buildworld failure: ifieee80211.c:(.text+0xeb7b): undefined reference to

Am Mon, 30 Nov 2015 08:35:30 -0800 NGie Cooper schrieb: > > On Nov 30, 2015, at 02:36, O. Hartmann wrote: > > > > It is hard to build a biuldworld buildkernel system these days :-( > > […] > > … > > Hi, > This issue should be fixed in r291491. > Thanks, > -NGie Great! Thank you. oh

Re: r 291486: buildworld failure: ifieee80211.c:(.text+0xeb7b): undefined reference to

> On Nov 30, 2015, at 02:36, O. Hartmann wrote: > > It is hard to build a biuldworld buildkernel system these days :-( > […] … Hi, This issue should be fixed in r291491. Thanks, -NGie ___ freebsd-current@freebsd.org mailing list https://lists

r 291486: buildworld failure: ifieee80211.c:(.text+0xeb7b): undefined reference to

It is hard to build a biuldworld buildkernel system these days :-( [...] --- all_subdir_secure --- cc -pg -O2 -pipe -O3 -O3 -pipe -march=native -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -DTERMIOS -DANSI_SOURCE -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DOPENSSL_IA32_S

Re: [CURRENT] buildworld failure: pfkeyv2.h:230:10: error: expected parameter declarator

On Fri, Jul 31, 2015 at 07:57:20AM +0200, O. Hartmann wrote: > CURRENT (r286107) fails in buildworld with the error shown below: > > --- all_subdir_libipsec --- > In file included from /usr/src/lib/libipsec/ipsec_strerror.c:39: > In file included from /usr/obj/usr/src/tmp/usr/include/netipsec/ipse

[CURRENT] buildworld failure: pfkeyv2.h:230:10: error: expected parameter declarator

CURRENT (r286107) fails in buildworld with the error shown below: --- all_subdir_libipsec --- In file included from /usr/src/lib/libipsec/ipsec_strerror.c:39: In file included from /usr/obj/usr/src/tmp/usr/include/netipsec/ipsec.h:45: /usr/obj/usr/src/tmp/usr/include/net/pfkeyv2.h:230:10: error: e

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

> On Jun 15, 2015, at 06:35, O. Hartmann wrote: > > On Sun, 14 Jun 2015 23:17:59 -0700 > Garrett Cooper wrote: > >>> On Jun 14, 2015, at 23:15, O. Hartmann wrote: >>> >>> Recent source of CURRENT (r284404) fails to buildworld when option >>> >>> CXXFLAGS+= -std=c++11 in /etc/src

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

On Sun, 14 Jun 2015 23:17:59 -0700 Garrett Cooper wrote: > On Jun 14, 2015, at 23:15, O. Hartmann wrote: > > > Recent source of CURRENT (r284404) fails to buildworld when option > > > > CXXFLAGS+= -std=c++11 in /etc/src.conf > > > > is given in /etc/src.conf. That issue was introd

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

e wasn't present. > > *PLEASE* file a bug. Done so as requested: Bug 200868 - [CURRENT r284407] buildworld failure due to missing #includes and weird share/mk issues ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/l

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

I’m experiencing the same issues with make buildkernel / make buildworld (r284402+) - no src.conf, always with a fresh source tree - lots of issues with mk and depends such as: make[1]: stopped in /usr/src .CURDIR='/usr/src' .MAKE='make' .OBJDIR='/usr/obj/usr/src' .TARGETS='buildworld' DESTDIR=

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

On Mon, 15 Jun 2015 08:15:52 +0200 "O. Hartmann" wrote: > Recent source of CURRENT (r284404) fails to buildworld when option > > CXXFLAGS+= -std=c++11 in /etc/src.conf > > is given in /etc/src.conf. That issue was introduced around after > r282336. Below, you'll se the src.conf I u

Re: [CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

On Jun 14, 2015, at 23:15, O. Hartmann wrote: > Recent source of CURRENT (r284404) fails to buildworld when option > > CXXFLAGS+= -std=c++11 in /etc/src.conf > > is given in /etc/src.conf. That issue was introduced around after > r282336. Below, you'll se the src.conf I use. I also

[CURRENT] r284404 buildworld failure due to CXXFLAGS+= -std=c++11 in /etc/src.conf

Recent source of CURRENT (r284404) fails to buildworld when option CXXFLAGS+= -std=c++11 in /etc/src.conf is given in /etc/src.conf. That issue was introduced around after r282336. Below, you'll se the src.conf I use. I also have the buildworl d failure with src.conf containing only

Re: [283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

On May 20, 2015, at 6:09, Garrett Cooper wrote: > On May 20, 2015, at 5:49, David Wolfskill wrote: > >> On Wed, May 20, 2015 at 06:50:24AM +0200, O. Hartmann wrote: >>> Current sources (r283136) die on buildworld with the following error: >>> >>> [...] >>> --- cddl/lib__L --- >>> /usr/obj/usr/

Re: [283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

On Wed, May 20, 2015 at 06:09:16AM -0700, Garrett Cooper wrote: > On May 20, 2015, at 5:49, David Wolfskill wrote: > > > On Wed, May 20, 2015 at 06:50:24AM +0200, O. Hartmann wrote: > >> Current sources (r283136) die on buildworld with the following error: > >> > >> [...] > >> --- cddl/lib__L --

Re: [283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

On May 20, 2015, at 5:49, David Wolfskill wrote: > On Wed, May 20, 2015 at 06:50:24AM +0200, O. Hartmann wrote: >> Current sources (r283136) die on buildworld with the following error: >> >> [...] >> --- cddl/lib__L --- >> /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc >> cc: error: linker

Re: [283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

On Wed, May 20, 2015 at 06:50:24AM +0200, O. Hartmann wrote: > Current sources (r283136) die on buildworld with the following error: > > [...] > --- cddl/lib__L --- > /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc > cc: error: linker command failed with exit code 1 (use -v to see invocation)

[283136]: buildworld failure: usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc

Current sources (r283136) die on buildworld with the following error: [...] --- cddl/lib__L --- /usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lproc cc: error: linker command failed with exit code 1 (use -v to see invocation) *** [libdtrace.so.2] Error code 1 ___

buildworld failure on 10.1 - Please advise

Hello everyone I beg to be advised on what I should do to solve why my attempts at buildworld on 10.1-RELEASE fail as follows: ===> gnu/usr.bin/gperf (obj,depend,all,install) ===> gnu/usr.bin/gperf/doc (obj) /usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/gperf/doc created for /usr/src/gnu/usr.bin/gper

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

On 04 Mar 2015, at 22:31, Dimitry Andric wrote: ... > Hmm, I've now seen that there many more ATF_REQUIRE_EQ() instance in the > tests, which compare against NULL. It is rather cumbersome to fix all > those, so maybe it should be fixed in atf-c++ instead. It turns out there aren't so many after

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

On 04 Mar 2015, at 21:19, Dimitry Andric wrote: > > On 04 Mar 2015, at 18:18, O. Hartmann wrote: >> >> Am Wed, 4 Mar 2015 14:10:00 +0100 >> Dimitry Andric schrieb: >> >>> On 04 Mar 2015, at 12:31, O. Hartmann wrote: On Mon, 2 Mar 2015 08:58:05 -0500 Ryan Stone wrote: > C

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

On 04 Mar 2015, at 18:18, O. Hartmann wrote: > > Am Wed, 4 Mar 2015 14:10:00 +0100 > Dimitry Andric schrieb: > >> On 04 Mar 2015, at 12:31, O. Hartmann wrote: >>> On Mon, 2 Mar 2015 08:58:05 -0500 >>> Ryan Stone wrote: >>> Can you post the contents of your make.conf and src.conf? I did

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

Am Wed, 4 Mar 2015 14:10:00 +0100 Dimitry Andric schrieb: > On 04 Mar 2015, at 12:31, O. Hartmann wrote: > > On Mon, 2 Mar 2015 08:58:05 -0500 > > Ryan Stone wrote: > > > > > Can you post the contents of your make.conf and src.conf? I didn't > > > see this in any of my "make tinderbox" runs >

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

Am Wed, 4 Mar 2015 14:10:00 +0100 Dimitry Andric schrieb: > On 04 Mar 2015, at 12:31, O. Hartmann wrote: > > On Mon, 2 Mar 2015 08:58:05 -0500 > > Ryan Stone wrote: > > > > > Can you post the contents of your make.conf and src.conf? I didn't > > > see this in any of my "make tinderbox" runs >

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

I don't think that libnv is the problem. It looks like a problem with atf-c++ to me. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@free

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

On 04 Mar 2015, at 12:31, O. Hartmann wrote: > On Mon, 2 Mar 2015 08:58:05 -0500 > Ryan Stone wrote: > > > Can you post the contents of your make.conf and src.conf? I didn't > > see this in any of my "make tinderbox" runs > > ___ > > freebsd-current@f

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2 Mar 2015 08:58:05 -0500 Ryan Stone wrote: > Can you post the contents of your make.conf and src.conf? I didn't > see this in any of my "make tinderbox" runs > ___ > freebsd-current@freebsd.org

Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

Can you post the contents of your make.conf and src.conf? I didn't see this in any of my "make tinderbox" runs ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebs

r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '<<' is ambiguous

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Buildworld fails in CURRENT r279514 with the following error: [...] - --- sbin.all__D --- - --- camcontrol.o --- cc -O2 -pipe -O3 -O3 -pipe -march=native -std=gnu99 -fstack-protector - -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused

Re: Buildworld Failure

Shawn Webb gmail.com> writes: Good Morning, > make[5]: make[5]: don't know how to make > /jenkins/usr/local/jenkins/workspace/HardenedBSD- Master/rescue/rescue//usr/local/jenkins/workspace/HardenedBSD- Master/bin/cat/cat.o. I am facing the same issue and it seems to be related to setting a cus

Re: Buildworld Failure

On Sat, Oct 4, 2014 at 8:30 PM, Shawn Webb wrote: > It looks like buildworld is failing when building the rescue binaries. I'm > not sure which commit broke it. Log is here: > http://0xfeedface.org/~shawn/2014-10-04-build.txt > The build is erroring out when trying to build the crunchgen'd cat f

Buildworld Failure

It looks like buildworld is failing when building the rescue binaries. I'm not sure which commit broke it. Log is here: http://0xfeedface.org/~shawn/2014-10-04-build.txt Thanks, Shawn ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org

Re: buildworld failure: pfvar.h:44 #include not found

Gleb Smirnoff wrote, On 10/29/2013 14:43: d> ===> usr.sbin/tcpdump/tcpdump (depend) +1 patch Success! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cu

Re: buildworld failure: pfvar.h:44 #include not found

On Tue, Oct 29, 2013 at 02:36:17PM +0100, d...@gmx.com wrote: d> Gleb Smirnoff wrote, On 10/29/2013 05:19: d> > +1 patch. d> So far, so good: d> d> ===> usr.sbin/tcpdump/tcpdump (depend) +1 patch -- Totus tuus, Glebius. Index: contrib/tcpdump/print-ip.c =

Re: buildworld failure: pfvar.h:44 #include not found

Gleb Smirnoff wrote, On 10/29/2013 05:19: +1 patch. So far, so good: ===> usr.sbin/tcpdump/tcpdump (depend) rm -f version.c ; sed 's/.*/char version[] = "&";/' /usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/VERSION > version.c rm -f .depend CC='/i/a/clang --sysroot=/usr/obj/usr/

Re: buildworld failure: pfvar.h:44 #include not found

On Tue, Oct 29, 2013 at 01:36:22AM +0100, d...@gmx.com wrote: d> Gleb Smirnoff wrote, On 10/28/2013 23:33: d> > Can you please test attached patch? d> d> Progress: d> ===> usr.bin/netstat (depend) d> rm -f .depend d> CC='/i/a/clang --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin' mk

Re: buildworld failure: pfvar.h:44 #include not found

Gleb Smirnoff wrote, On 10/28/2013 23:33: Can you please test attached patch? Progress: ===> usr.bin/netstat (depend) rm -f .depend CC='/i/a/clang --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin' mkdep -f .depend -a-DIPSEC -DSCTP -DINET -DNDEBUG -std=gnu99 /usr/src/usr.bi

Re: buildworld failure: pfvar.h:44 #include not found

On Mon, Oct 28, 2013 at 11:14:57PM +0100, d...@gmx.com wrote: d> ===> sbin/ifconfig (depend) d> rm -f .depend d> CC='/path/to/clang --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin' mkdep -f .depend -a-DINET -DNDEBUG -std=gnu99 /usr/src/sbin/ifconfig/ifconfig.c /usr/src/sbin/if

buildworld failure: pfvar.h:44 #include not found

===> sbin/ifconfig (depend) rm -f .depend CC='/path/to/clang --sysroot=/usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/bin' mkdep -f .depend -a-DINET -DNDEBUG -std=gnu99 /usr/src/sbin/ifconfig/ifconfig.c /usr/src/sbin/ifconfig/af_link.c /usr/src/sbin/ifconfig/af_inet.c /usr/src/sbin/ifcon

buildworld failure

FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #78 r253966: Mon Aug 5 14:42:05 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 # svn info Path: . Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/bas

Re: strange buildworld failure

On Sat, 24 Nov 2012, Garrett Cooper wrote: On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk wrote: On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: By the way, I tried to add some debugging info with the help of make -d A or -d g2 but the amount of logging was excessive(the build was ran in a tmux

Re: strange buildworld failure

On Nov 24, 2012, at 11:48 AM, Benjamin Kaduk wrote: > On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: > >> On 11/24/2012 1:45 PM, Dimitry Andric wrote: >>> On 2012-11-24 03:38, Benjamin Kaduk wrote: Hmm, buildworld is supposed to be parallel-make-safe. Perhaps a full log of the failing b

Re: strange buildworld failure

On Sat, 24 Nov 2012, Nikos Vassiliadis wrote: On 11/24/2012 1:45 PM, Dimitry Andric wrote: On 2012-11-24 03:38, Benjamin Kaduk wrote: Hmm, buildworld is supposed to be parallel-make-safe. Perhaps a full log of the failing buildworld (e.g., with script(1)) could be posted for analysis? Well,

Re: strange buildworld failure

On 11/24/2012 1:45 PM, Dimitry Andric wrote: On 2012-11-24 03:38, Benjamin Kaduk wrote: On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: Also, my src.conf had WITHOUT_CLANG but I deleted it and then I also deleted /usr/obj when it failed for the firs

Re: strange buildworld failure

On 2012-11-24 03:38, Benjamin Kaduk wrote: On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: Also, my src.conf had WITHOUT_CLANG but I deleted it and then I also deleted /usr/obj when it failed for the first time. But that didn't work. I am building wi

Re: strange buildworld failure

On Fri, 23 Nov 2012, Nikos Vassiliadis wrote: On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: Also, my src.conf had WITHOUT_CLANG but I deleted it and then I also deleted /usr/obj when it failed for the first time. But that didn't work. I am building with -j3. Does it always fail there at usr.

Re: strange buildworld failure

On 11/23/2012 1:34 PM, Sergey Kandaurov wrote: Also, my src.conf had WITHOUT_CLANG but I deleted it and then I also deleted /usr/obj when it failed for the first time. But that didn't work. I am building with -j3. Does it always fail there at usr.bin/ypwhich? It's likely that -j3 is the culprit

Re: strange buildworld failure

On 23 November 2012 12:34, Nikos Vassiliadis wrote: > Hi, > > I am trying to buildworld but it fails here: >> >> ===> usr.bin/ypwhich (all) >> cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector >> -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - >> Wno-pointer-sign -W

strange buildworld failure

Hi, I am trying to buildworld but it fails here: ===> usr.bin/ypwhich (all) cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized - Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unu

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

On 03/05/12 08:45, Dimitry Andric wrote: > On 2012-03-05 00:40, O. Hartmann wrote: > ... >> All right, my /etc/src.conf looks like this now (as it does before): >> >> WITH_CLANG= YES >> WITH_CLANG_EXTRAS= YES >> # >> WITH_BIND_LIBS= YES >> WITH_BIND_SIGCHASE= YES >> WIT

Re: CLANG buildworld failure: lint: cannot exec /usr/obj/usr/src/tmp/usr/bin/cc: No such file or directory

On 2012-03-05 00:40, O. Hartmann wrote: ... > All right, my /etc/src.conf looks like this now (as it does before): > > WITH_CLANG= YES > WITH_CLANG_EXTRAS= YES > # > WITH_BIND_LIBS= YES > WITH_BIND_SIGCHASE= YES > WITH_BIND_LARGE_FILE= YES > # > WITH_IDEA=

  1   2   3   4   >