Re: buildworld error

te: > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > ===> stand/i386/pxeldr (all) > > > > `kldstat.o' is up to date. > > > > -14152 bytes available > > > > > > > > The same ha

Re: buildworld error

te: > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > ===> stand/i386/pxeldr (all) > > > > `kldstat.o' is up to date. > > > > -14152 bytes available > > > > > > > > The same ha

Re: buildworld error

Gordon Bergling writes: > But I wonder why I am the only person, who hits that problem since it > is a very plain -CURRENT build on a Hyper-V instance. You enabled BearSSL (and consequently Veriexec), that's pretty far from a plain build. The fact that you don't realize this leads me to suspect

Re: buildworld error

t; > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling > wrote: > > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > > > ===> stand/i386/pxeldr (all) > > > > > `kldstat.o' is up to date. > > &g

Re: buildworld error

Hi Warner, On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote: > On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote: > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote: > > > >

Re: buildworld error

On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote: > Hi Warner, > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote: > > > I got the following buildworld error a recent -CURRENT > > >

Re: buildworld error

Hi Warner, On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote: > > I got the following buildworld error a recent -CURRENT > > > > ===> stand/i386/pxeldr (all) > > `kldstat.o' is up to date. >

Re: buildworld error

On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote: > Hi folks, > > I got the following buildworld error a recent -CURRENT > > ===> stand/i386/pxeldr (all) > `kldstat.o' is up to date. > -14152 bytes available > > The same happens on stable/14: > > ==

buildworld error

Hi folks, I got the following buildworld error a recent -CURRENT ===> stand/i386/pxeldr (all) `kldstat.o' is up to date. -14152 bytes available The same happens on stable/14: ===> stand/i386/pxeldr (all) -22344 bytes available ===> share/misc (all) --- loader --- *** [loader

RES: i made a mess (forgot the buildworld and installworld)

> Assunto: Re: i made a mess (forgot the buildworld and installworld) > > Hello! > > > I made a big mess here. > > I (deleted my system libraries) > > If I have no snapshots: > - boot into the installer > - mount > - copy /usr/* > > It's not

Re: i made a mess (forgot the buildworld and installworld)

Am 2024-07-15 03:05, schrieb Alexander Ziaee: Eventually, you want to learn to snapshot your system when you're touching critical directories. Then, it never matters. You can just roll back stressfree. Specific to updates and if on ZFS: man bectl Even better than snapshots. Bye, Alexander.

Re: i made a mess (forgot the buildworld and installworld)

Hello! > I made a big mess here. > I (deleted my system libraries) If I have no snapshots: - boot into the installer - mount - copy /usr/* It's not good, but it's good enough to get going to restore from backup or makeworld at your leisure. Eventually, you want to learn to snapshot your system

RES: RES: i made a mess (forgot the buildworld and installworld)

; Para: Ivan Quitschal > Cc: freebsd-current@freebsd.org > Assunto: Re: RES: i made a mess (forgot the buildworld and installworld) > > On 2024-07-14 09:54, Ivan Quitschal wrote: > > One idea > > Cant say it that would help , but ive checked here and 2 things are > > working

Re: RES: i made a mess (forgot the buildworld and installworld)

> > > > > > > > De: owner-freebsd-curr...@freebsd.org > > Em nome de Ivan Quitschal > > Enviada em: sábado, 13 de julho de 2024 22:05 > > Para: freebsd-current@freebsd.org > > Assunto: i made a mess (forgot the buildworld and installworld) > >

Re: RES: i made a mess (forgot the buildworld and installworld)

> thank you again > > Ivan > > > > De: owner-freebsd-curr...@freebsd.org Em > nome de Ivan Quitschal > Enviada em: sábado, 13 de julho de 2024 22:05 > Para: freebsd-current@freebsd.org > Assunto: i made a mess (forgot the buildworld and installworld) > >

RES: i made a mess (forgot the buildworld and installworld)

g Em nome de Ivan Quitschal Enviada em: sábado, 13 de julho de 2024 22:05 Para: freebsd-current@freebsd.org Assunto: i made a mess (forgot the buildworld and installworld) Hi all I made a big mess here. Please lets see if you guys have any idea I did a make buildkernel make installkernel

i made a mess (forgot the buildworld and installworld)

Hi all I made a big mess here. Please lets see if you guys have any idea I did a make buildkernel make installkernel Then forgot the buildworld And went straight to make delete-old make delete-old-libs now not even git command, or ports or nothing because everything is missing on libraries

Re: Buildworld stops for d3befb534b9 in tests

On Mon, Mar 04, 2024 at 09:54:14AM -0800, Mark Millard wrote: > bob prohaska wrote on > Date: Mon, 04 Mar 2024 16:35:52 UTC : > > > An armv7 (Pi2 v1.1) -current system stopped buildworld with > > > > c++: error: linker command failed with exit code 1 (us

Re: Buildworld stops for d3befb534b9 in tests

bob prohaska wrote on Date: Mon, 04 Mar 2024 16:35:52 UTC : > An armv7 (Pi2 v1.1) -current system stopped buildworld with > > c++: error: linker command failed with exit code 1 (use -v to see invocation) > *** [capsicum-test.full] Error code 1 There might have been more error mess

Buildworld stops for d3befb534b9 in tests

An armv7 (Pi2 v1.1) -current system stopped buildworld with c++: error: linker command failed with exit code 1 (use -v to see invocation) *** [capsicum-test.full] Error code 1 make[6]: stopped in /usr/src/tests/sys/capsicum .ERROR_TARGET='capsicum-test.full' .ERROR_META_FILE='/

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: make buildworld puts legacy tools into the /usr/obj/... tree

t; > > > I did, based of a git clone of head, a clean compile of world and kernel > > with > > > > # cd /usr > > # rm -rf obj > > # mkdir obj > > # cd src > > # make -j8 buildworld > > # make -j8 buildkernel > > ... > > I installed

Re: make buildworld puts legacy tools into the /usr/obj/... tree

El día domingo, agosto 06, 2023 a las 10:12:03a. m. -0600, Warner Losh escribió: > So what's the vintage of the host you are building with? And what sources > are > you building... The vintage was (now updated): 13.0-CURRENT 1300130 r368164 and /usr/src was git cloned from yesterday's head.

Re: make buildworld puts legacy tools into the /usr/obj/... tree

, a clean compile of world and > kernel > > > with > > > > > > # cd /usr > > > # rm -rf obj > > > # mkdir obj > > > # cd src > > > # make -j8 buildworld > > > # make -j8 buildkernel > > > ... > > > I installed

Re: make buildworld puts legacy tools into the /usr/obj/... tree

# rm -rf obj > > # mkdir obj > > # cd src > > # make -j8 buildworld > > # make -j8 buildkernel > > ... > > I installed the result and the system runs fine. For some test I wanted > > to do another installation to some DESTDIR with > > > > # make in

Re: make buildworld puts legacy tools into the /usr/obj/... tree

On Sun, Aug 6, 2023 at 7:58 AM Matthias Apitz wrote: > > I did, based of a git clone of head, a clean compile of world and kernel > with > > # cd /usr > # rm -rf obj > # mkdir obj > # cd src > # make -j8 buildworld > # make -j8 buildkernel > ... > I installed

make buildworld puts legacy tools into the /usr/obj/... tree

I did, based of a git clone of head, a clean compile of world and kernel with # cd /usr # rm -rf obj # mkdir obj # cd src # make -j8 buildworld # make -j8 buildkernel ... I installed the result and the system runs fine. For some test I wanted to do another installation to some DESTDIR with

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #5 from Yuri Victorovich --- (In reply to Mark Millard from comment #4) > Being in a VirtualBox VM the /dev/ada0p2 may not indicate > much about the actual media involved. The physical medium is a traditional spinning HD with

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #4 from Mark Millard --- (In reply to Yuri Victorovich from comment #2) Being in a VirtualBox VM the /dev/ada0p2 may not indicate much about the actual media involved. Microsd card and spinning rust media are more likely than s

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #3 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) > Do you have anything specific for what controls getting [...]. This is a generic install. No specific options of any kind were set. -- You are receivi

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 --- Comment #2 from Yuri Victorovich --- (In reply to Mark Millard from comment #1) Swap is on /dev/ada0p2. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Commen

[Bug 272536] 'make buildworld -j 8' fails: pid 79018 (clang), jid 0, uid 0, was killed: a thread waiting too long to allocate a page

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272536 Yuri Victorovich changed: What|Removed |Added URL||https://people.freebsd.org/

Re: buildworld broken due to INET6 not being set

On Tue, 4 Jul 2023 16:48:10 + Gary Jennejohn wrote: > buildworld breaks because I do not have INET6 defined: > > /usr/src/sbin/ping/main.c:76:7: error: variable 'ipv4' set but not used > [-Werror,-Wunused-but-set-variable] > bool ipv4 = false; >

buildworld broken due to INET6 not being set

buildworld breaks because I do not have INET6 defined: /usr/src/sbin/ping/main.c:76:7: error: variable 'ipv4' set but not used [-Werror,-Wunused-but-set-variable] bool ipv4 = false; ^ 1 error generated. ipv4 is set in various places but it's _used_ only b

651d1efd96a6 buildworld failed, cd9da8d072e4 succeeded

On 29/06/2023 19:16, Graham Perrin wrote: % uname -KU 1400092 1400090 % uname -a FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n263799-f81be7a8318b-dirty: Mon Jun 26 22:09:58 BST 2023 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC

651d1efd96a6 buildworld failed

% uname -KU 1400092 1400090 % uname -a FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n263799-f81be7a8318b-dirty: Mon Jun 26 22:09:58 BST 2023 grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 % bectl list -c creation | tail -n

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/

addition of pflog_if_print to the tcpdump code can break buildworld

The addition of pflog_if_print to the tcpdump code breaks buildworld if WITHOUT_PF= is set in /etc/src.conf. I do not use PF and have WITHOUT_PF= set in /etc/src.conf. If I comment out WITHOUT_PF= buildworld succeeds. But I have no use for PF and don't want to build it. Here's the

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: continuing 14-CURRENT buildworld error...

On Tue, 28 Feb 2023 00:23:59 -0800 (PST), "Jeffrey Bouquet" wrote: > in src.conf: > > WITHOUT_TFTP= > > nevertheless, the buildworld halts in building tftp-proxy... > > .. > OR it halts with too may of the below errors: the buildworld doesn&#x

continuing 14-CURRENT buildworld error...

in src.conf: WITHOUT_TFTP= nevertheless, the buildworld halts in building tftp-proxy... .. OR it halts with too may of the below errors: the buildworld doesn't inform which process stopped it. ld.lld error: undefined symbol FreeBSD_nvlist_* [ many undefined symbols each starting

Re: buildworld failure

/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/libexec::/usr/obj/usr/src/amd64.amd64/tmp/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/u

Re: core dump in ld during buildworld

obj/usr/src/amd64.amd64/tmp/obj-tools/usr.bin/clang/llvm-tblgen/llvm-tblgen > make -C /usr/src/lib/clang/libllvm > make -C /usr/src/usr.bin/clang/lld > > If that works, you can run make install from usr.bin/clang/lld. > Thanks for the hints. The above got me past the segfault in ld.ldd. I now have an error about libdwarf.a being truncated and extended beyond some limit while building nm. I'm simply do 'make -k buildworld' now to see if anything is running south. -- Steve

Re: core dump in ld during buildworld

On 19 Feb 2023, at 06:15, Steve Kargl wrote: > > On Sat, Feb 18, 2023 at 04:57:45PM -0800, Steve Kargl wrote: >>> >>> At that point it is still using the system compiler and linker, and it >>> seems that the latter is lld. Do you know which version it is? >>> >> >> Good question. Unfortunate

Re: core dump in ld during buildworld

On Sat, Feb 18, 2023 at 04:57:45PM -0800, Steve Kargl wrote: > > > > At that point it is still using the system compiler and linker, and it > > seems that the latter is lld. Do you know which version it is? > > > > Good question. Unfortunate ident(1) is useless in a git world. > > % ll /usr/bi

Re: core dump in ld during buildworld

On Sun, Feb 19, 2023 at 01:50:07AM +0100, Dimitry Andric wrote: > On 19 Feb 2023, at 01:33, Steve Kargl > wrote: > > > > During biuldworld, > > > > ==> usr.bin/nm (obj,all,install) > > cc -O2 -pipe -g -fno-common -I/usr/src/contrib/elftoolchain/libelftc > > -I/usr/src/contrib/elftoolchain/comm

Re: core dump in ld during buildworld

On 19 Feb 2023, at 01:33, Steve Kargl wrote: > > During biuldworld, > > ==> usr.bin/nm (obj,all,install) > cc -O2 -pipe -g -fno-common -I/usr/src/contrib/elftoolchain/libelftc > -I/usr/src/contrib/elftoolchain/common -std=gnu99 -Wno-format-zero-length > -Wsystem-headers -Wall -Wno-format-y2k -

core dump in ld during buildworld

During biuldworld, ==> usr.bin/nm (obj,all,install) cc -O2 -pipe -g -fno-common -I/usr/src/contrib/elftoolchain/libelftc -I/usr/src/contrib/elftoolchain/common -std=gnu99 -Wno-format-zero-length -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-proto

Re: buildworld failure

legacy/usr/libexec::/usr/obj/usr/src/amd64.amd64/tmp/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/a

Re: buildworld failure

usr/obj/usr/src/amd64.amd64/tmp/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/le

buildworld failure

in:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin' SRCTOP='/usr/src' OBJTOP='/usr/obj/usr/src/amd64.amd64 . Anyone see/know anything causing this error? Also, the buildworld command most likely to build the most amd64 components from scratch?

Re: devel/freebsd-gcc12 based aarch64 nono-debug buildworld buildkernel: a Failure notice at/for stand/kboot/loader.kboot

hat this is part of why devel/gcc* ports exist. Otherwise: why have them? > On Fri, Feb 10, 2023 at 8:42 PM Mark Millard wrote: > self hosted aarch64 Non-debug buildworld Failure notice (from the .meta file): > > . . . > /usr/local/libexec/gcc/aarch64-unknown-freebsd14.0/12.1.0/colle

Re: devel/freebsd-gcc12 based aarch64 nono-debug buildworld buildkernel: a Failure notice at/for stand/kboot/loader.kboot

rk Millard wrote: > self hosted aarch64 Non-debug buildworld Failure notice (from the .meta > file): > > . . . > /usr/local/libexec/gcc/aarch64-unknown-freebsd14.0/12.1.0/collect2 -plugin > /usr/local/libexec/gcc/aarch64-unknown-freebsd14.0/12.1.0/liblto_plugin.so > -plugin-opt

devel/freebsd-gcc12 based aarch64 nono-debug buildworld buildkernel: a Failure notice at/for stand/kboot/loader.kboot

self hosted aarch64 Non-debug buildworld Failure notice (from the .meta file): . . . /usr/local/libexec/gcc/aarch64-unknown-freebsd14.0/12.1.0/collect2 -plugin /usr/local/libexec/gcc/aarch64-unknown-freebsd14.0/12.1.0/liblto_plugin.so -plugin-opt=/usr/local/libexec/gcc/aarch64-unknow n

devel/freebsd-gcc12 based amd64 buildworld buildkernel: a Failure notice ( non-debug buildworld ) + Messages ( buildkernel 's)

Non-debug buildworld Failure notice : /usr/local/bin/x86_64-unknown-freebsd14.0-ld: /usr/obj/BUILDs/main-amd64-nodbg-gccxtc/usr/main-src/amd64.amd64/lib/libblacklist/libblacklist.a(bl.o): relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with

Re: buildworld failed after deleting /usr/obj

- Original Message --- On Sunday, January 29th, 2023 at 3:06 PM, qroxana wrote: > It appears buildworld doesn't create the obj directory for > usr.bin/clang/llvm-objcopy in stage 2.2 after this commit. > > commit adc3c128c6603054586a993d117e5dd808deac17 > Au

Re: buildworld failed after deleting /usr/obj

> > > > -Dimitry > > > I had tried it with a clean source directory and empty /usr/obj > > # find /usr/src/usr.bin/clang/llvm-objcopy > /usr/src/usr.bin/clang/llvm-objcopy > /usr/src/usr.bin/clang/llvm-objcopy/llvm-objcopy.1 > /usr/src/usr.bin/clang/llvm-o

Re: buildworld failed after deleting /usr/obj

from the top level, or clean up > your source checkout with something like "git clean". > > -Dimitry I had tried it with a clean source directory and empty /usr/obj # find /usr/src/usr.bin/clang/llvm-objcopy /usr/src/usr.bin/clang/llvm-objcopy /usr/src/usr.bin/clang/llvm-obj

Re: buildworld failed after deleting /usr/obj

On 23 Jan 2023, at 04:05, qroxana wrote: > > It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy. > > --- all_subdir_usr.bin --- > --- objwarn --- > Warning: Object directory not changed from original > /usr/src/usr.bin/clang/llvm-objcopy This is usually an indication that yo

buildworld failed after deleting /usr/obj

It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy. --- all_subdir_usr.bin --- --- objwarn --- Warning: Object directory not changed from original /usr/src/usr.bin/clang/llvm-objcopy --- COFF/COFFObjcopy.o --- c++ -target aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/

Re: buildworld fail: ld: error: undefined symbol: test_no_kevents

> Am 06.06.2022 um 13:42 schrieb Ronald Klop : > > > ….. Will take 10+ hours to compile clang for the millionth time. > I also often prefer compiling on target hardware… but to be honest: cross compiling on -j(fullspeed)-machines to PXE-boot one slow boards is the only „painless" workflow.

Re: buildworld fail: ld: error: undefined symbol: test_no_kevents

ionth time. Ronald. [1] https://en.wiktionary.org/wiki/PEBCAK Van: Dimitry Andric Datum: maandag, 6 juni 2022 12:16 Aan: Ronald Klop CC: freebsd-current , Mark Johnston Onderwerp: Re: buildworld fail: ld: error: undefined symbol: test_no_kevents Looks like it might be using an old version of

Re: buildworld fail: ld: error: undefined symbol: test_no_kevents

> Am 06.06.2022 um 11:59 schrieb Ronald Klop : > > on my rpi4….. > 10:04:45 > 10:04:45 > ld: error: undefined symbol: kevent_cmp > > Any thoughts? Similar experience? > > Yes, similar experience(~1 week ago) , specially when using NO_CLEAN flag , as far as I remember.. `got around this

Re: buildworld fail: ld: error: undefined symbol: test_no_kevents

Looks like it might be using an old version of tests/sys/kqueue/libkqueue/common.h, after https://cgit.freebsd.org/src/commit/?id=c728c56c870abe230e45cee5c477f0d890ebacef ? Without seeing how the .o files have been compiled, specifically with which -I flags, it is impossible to see what is goi

buildworld fail: ld: error: undefined symbol: test_no_kevents

Hi, Building on aarch64/14-CURRENT fails with this error on my rpi4. It failed on incremental build and tried a clean build today. First failure was on "World build started on Sun May 29 00:25:17 UTC 2022". This weekend it still fails (I'm building weekly in Jenkins). 10:04:44 ===> tests/sys/kq

Buildworld stops with ld: error: undefined symbol: AcpiWarning on -current

A Pi3 running -current is stopping with ld: error: undefined symbol: AcpiWarning during buildworld. The sources are up-to- date as of a few minutes ago. A series of related "Acpi..." errors follow. The build command line is make -j2 -DWITH_META_MODE buildworld > buildworld.lo

Re: Buildworld fails with external GCC toolchain

From: Yasuhiro Kimura Subject: Re: Buildworld fails with external GCC toolchain Date: Tue, 15 Feb 2022 08:26:00 +0900 (JST) >> I have amd64 world + kernel building with GCC 9 and the only remaining >> open review not merged yet is https://reviews.freebsd.org/D34147. >> >&g

Re: Buildworld fails with external GCC toolchain

From: John Baldwin Subject: Re: Buildworld fails with external GCC toolchain Date: Mon, 14 Feb 2022 10:46:29 -0800 >>> Not really, the gcc 9 build has been broken for months, as far as I >>> know. >>> >>> See also: https://ci.freebsd.org/job/FreeBSD-main-amd6

Re: Buildworld fails with external GCC toolchain

On 2/12/22 11:34 AM, Yasuhiro Kimura wrote: From: Dimitry Andric Subject: Re: Buildworld fails with external GCC toolchain Date: Fri, 11 Feb 2022 22:53:44 +0100 Not really, the gcc 9 build has been broken for months, as far as I know. See also: https://ci.freebsd.org/job/FreeBSD-main-amd64

Re: Buildworld fails with external GCC toolchain

From: Dimitry Andric Subject: Re: Buildworld fails with external GCC toolchain Date: Fri, 11 Feb 2022 22:53:44 +0100 > Not really, the gcc 9 build has been broken for months, as far as I know. > > See also: https://ci.freebsd.org/job/FreeBSD-main-amd64-gcc9_build/ > > The last

Re: Buildworld fails with external GCC toolchain

stall amd64-gcc9 > 4. cd /usr/src > 5. make -j 4 CROSS_TOOLCHAIN=amd64-gcc9 buildworld buildkernel > > Then step 5 failed as following. > > -- > --- all_subdir_rescue --- > /usr/local/bin/x86_64-unknown-

Buildworld fails with external GCC toolchain

an install of 14-CURRENT amd64 with the install image of 20220210 snapshot. 2. Checkout latest main of src repository (d4b0fa45dc1 at that time). 3. pkg install amd64-gcc9 4. cd /usr/src 5. make -j 4 CROSS_TOOLCHAIN=amd64-gcc9 buildworld buildkernel Then step 5 failed as

Re: buildworld failed

S= WITHOUT_TESTS= The build command is: env MAKEOBJDIRPREFIX=$HOME/obj \     make -j2 \     -DNO_CLEAN \     __MAKE_CONF=$HOME/make.conf \     SRCCONF=$HOME/src.conf \     TARGET=amd64 \     TARGET_ARCH=amd64 \     CPUTYPE= \     buildworld Perhaps the issue is that I first build the tool

Re: test-includes breaks buildworld when WITHOUT_PF is set in src.conf

> > > > .if ${MK_PF} != "no" > > INCSGROUPS+= PF > > .endif > > > > This breaks buildworld. The error message: > > > > In file included from net_pfvar.c:1: > > /usr/obj/usr/src/amd64.amd64/tmp/usr/include/net/pfvar.h:65:10: fatal err

Re: test-includes breaks buildworld when WITHOUT_PF is set in src.conf

On 9 Feb 2022, at 10:57, Gary Jennejohn wrote: > test-includes uses pf.h when checking usage of pfvar.h. > > But, these lines in include/Makefile remove pf.h when WITHOUT_PF is > set in src.conf: > > .if ${MK_PF} != "no" > INCSGROUPS+= PF > .endif > > Th

test-includes breaks buildworld when WITHOUT_PF is set in src.conf

test-includes uses pf.h when checking usage of pfvar.h. But, these lines in include/Makefile remove pf.h when WITHOUT_PF is set in src.conf: .if ${MK_PF} != "no" INCSGROUPS+= PF .endif This breaks buildworld. The error message: In file included from net_pfvar.c:1: /usr/obj/usr

Re: buildworld failed

Brooks Davis wrote: > On Tue, Feb 08, 2022 at 02:52:27PM -0800, Simon J. Gerraty wrote: > > Brooks Davis wrote: > > > > > > This would be fine, but should not be necessicary. The sys subdir should > > > be created by AUTOOBJ. > > > > .OBJDIR should be (and is), not .OBJDIR/sys > > We've had s

Re: buildworld failed

On Tue, Feb 08, 2022 at 02:52:27PM -0800, Simon J. Gerraty wrote: > Brooks Davis wrote: > > > > This would be fine, but should not be necessicary. The sys subdir should > > be created by AUTOOBJ. > > .OBJDIR should be (and is), not .OBJDIR/sys We've had support for relative paths in SRCS since

Re: buildworld failed

I went ahead and committed this as 5ae6cc00111c since we chatted about it here. Warner On Tue, Feb 8, 2022 at 5:10 PM Warner Losh wrote: > > > On Tue, Feb 8, 2022 at 3:52 PM Simon J. Gerraty wrote: > >> Brooks Davis wrote: >> > >> > This would be fine, but should not be necessicary. The sys s

Re: buildworld failed

On Tue, Feb 8, 2022 at 3:52 PM Simon J. Gerraty wrote: > Brooks Davis wrote: > > > > This would be fine, but should not be necessicary. The sys subdir should > > be created by AUTOOBJ. > > .OBJDIR should be (and is), not .OBJDIR/sys > making that subdir is up to the makefile and would also fix t

Re: buildworld failed

Brooks Davis wrote: > > This would be fine, but should not be necessicary. The sys subdir should > be created by AUTOOBJ. .OBJDIR should be (and is), not .OBJDIR/sys making that subdir is up to the makefile and would also fix the problem, but given the nature of what the makefile is doing just r

Re: buildworld failed

Warner Losh wrote: > > Same here for me for the past couple of weeks. Haven't been able to > > identify why it fails. My hunch was that a particular objdir wasn't > > being created. As a workaround I edited the Makefile.inc1 to remove > > the test-includes command (line 1128 I think). > > The sys

Re: buildworld failed

On Tue, Feb 08, 2022 at 09:56:19AM -0800, Simon J. Gerraty wrote: > Warner Losh wrote: > > --- sys/abi_compat.c --- > > echo "#include " > sys/abi_compat.c > > sh: cannot create sys/abi_compat.c: No such file or directory > > *** [sys/abi_compat.c] Error code 2 > > > > make[4]: stopped in /usr/sr

Re: buildworld failed

On Tue, Feb 8, 2022 at 10:56 AM Simon J. Gerraty wrote: > Warner Losh wrote: > > --- sys/abi_compat.c --- > > echo "#include " > sys/abi_compat.c > > sh: cannot create sys/abi_compat.c: No such file or directory > > *** [sys/abi_compat.c] Error code 2 > > > > make[4]: stopped in /usr/src/tools/b

Re: buildworld failed

Warner Losh wrote: > --- sys/abi_compat.c --- > echo "#include " > sys/abi_compat.c > sh: cannot create sys/abi_compat.c: No such file or directory > *** [sys/abi_compat.c] Error code 2 > > make[4]: stopped in /usr/src/tools/build/test-includes > --- sys/acct.c --- > echo "#include " > sys/acct.c

Re: buildworld failed

On Tue, Feb 8, 2022 at 3:43 AM George Abdelmalik wrote: > > On 7/2/22 03:50, qroxana wrote: > > > > I know running make install for /usr/src/tools/build/test-includes can fix > this, > but this still fails on a newly installed 14.0-CURRENT. > > --- test-includes --- > cd /usr/src/tools/build/test

Re: buildworld failed

On 7/2/22 03:50, qroxana wrote: I know running make install for /usr/src/tools/build/test-includes can fix this, but this still fails on a newly installed 14.0-CURRENT. --- test-includes --- cd /usr/src/tools/build/test-includes; MACHINE_ARCH=aarch64 MACHINE=arm64  CPUTYPE= CC="cc -target

buildworld failed

I know running make install for /usr/src/tools/build/test-includes can fix this, but this still fails on a newly installed 14.0-CURRENT. --- test-includes --- cd /usr/src/tools/build/test-includes; MACHINE_ARCH=aarch64 MACHINE=arm64 CPUTYPE= CC="cc -target aarch64-unknown-freebsd14.0 --sysroot=/

Is amd64 buildworld supposed to be working for WITH_ASAN= WITH_UBSAN= (both used)? [It fails to link various things.]

lldb_private::lldb_renderscript::fixupX86FunctionCalls(llvm::Module&) . . . Is the "ObjC" related material and the "renderscript" related material even supposed to be referenced or linked in? If yes, what is missing to allow the links to complete. I've not tried to

Re: WITHOUT_PF breaks buildworld

On Wed, 22 Dec 2021 12:52:15 -0600 Warner Losh wrote: > On Wed, Dec 22, 2021, 12:37 PM Gary Jennejohn wrote: > [snip patch] > > > > Since pf.h is used so widely in the tree it's probably the simplest > > fix. > > > > > > > > > > I like this. I'd unconditionally remove the test in preferen

Re: WITHOUT_PF breaks buildworld

On Wed, Dec 22, 2021, 12:37 PM Gary Jennejohn wrote: > On Wed, 22 Dec 2021 10:58:50 -0600 > Warner Losh wrote: > > > On Wed, Dec 22, 2021, 10:02 AM Gary Jennejohn > wrote: > > > > > > > > This simple patch to /usr/src/include/Makefile fixes it for me: > > > > > > --- Makefile.orig 2021-12

Re: WITHOUT_PF breaks buildworld

On Wed, 22 Dec 2021 10:58:50 -0600 Warner Losh wrote: > On Wed, Dec 22, 2021, 10:02 AM Gary Jennejohn wrote: > > > > > This simple patch to /usr/src/include/Makefile fixes it for me: > > > > --- Makefile.orig 2021-12-22 13:37:02.817745000 +0100 > > +++ Makefile2021-12-22 13:37:12.1773

Re: WITHOUT_PF breaks buildworld

or > > > > > > > > Best regards, > > > > Konrad Sewi??o-Jopek > > > > > > > > > > > > niedz., 19 gru 2021 o 12:26 Gary Jennejohn > > > > napisa?(a): > > > > > > > >> On Sun, 19 Dec 2021 19:0

Re: WITHOUT_PF breaks buildworld

19:05:35 +0800 > > >> Alastair Hogge wrote: > > >> > > >>> On Sunday, 19 December 2021 6:47:23 PM AWST Gary Jennejohn wrote: > > >>>> Some recent change, probably in a .mk file, breaks builworld on HEAD > > >>>> whe

Re: WITHOUT_PF breaks buildworld

change, probably in a .mk file, breaks builworld on HEAD >>>> when WITHOUT_PF is enabled in src.conf. >>> >>> I have had to disable WITHOUT_PF since 2020-07-27, but probably earlier. >>> >> >> Hmm. I did a successful buildworld a few days ago with WITHOUT_

  1   2   3   4   5   6   7   8   9   10   >