Re: buildworld failed

2022-02-08 Thread George Abdelmalik


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 aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -target 
aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin" CXX="c++ -target 
aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin  -target 
aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin"  CPP="cpp -target 
aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -target 
aarch64-unknown-freebsd14.0 
--sysroot=/usr/obj/usr/src/arm64.aarch64/tmp 
-B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin"  AS="as" AR="ar" 
ELFCTL="elfctl" LD="ld"  LLVM_LINK="" NM=nm OBJCOPY="objcopy" 
RANLIB=ranlib STRINGS=  SIZE="size" STRIPBIN="strip" INSTALL="install 
-U" 
PATH=/usr/obj/usr/src/arm64.aarch64/tmp/bin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/libexec::/usr/obj/usr/src/arm64.aarch64/tmp/bin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin 
SYSROOT=/usr/obj/usr/src/arm64.aarch64/tmp make 
DESTDIR=/usr/obj/usr/src/arm64.aarch64/tmp test-includes

--- sys/abi_compat.c ---
--- sys/acct.c ---
--- sys/acl.c ---
--- sys/aio.c ---
--- 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
sh: cannot create sys/acct.c: No such file or directory
*** [sys/acct.c] Error code 2

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

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


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).


I'd really like to understand why this error comes about. If someone has 
any insights, please share them :)


Regards,
George.



Re: buildworld failed

2022-02-08 Thread Warner Losh
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-includes;  MACHINE_ARCH=aarch64
> MACHINE=arm64  CPUTYPE= CC="cc -target aarch64-unknown-freebsd14.0
> --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -target
> aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin" CXX="c++  -target
> aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin  -target
> aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin"  CPP="cpp -target
> aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -target
> aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp
> -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin"  AS="as" AR="ar"
> ELFCTL="elfctl" LD="ld"  LLVM_LINK="" NM=nm OBJCOPY="objcopy"
> RANLIB=ranlib STRINGS=  SIZE="size" STRIPBIN="strip"  INSTALL="install -U"
> PATH=/usr/obj/usr/src/arm64.aarch64/tmp/bin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/libexec::/usr/obj/usr/src/arm64.aarch64/tmp/bin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/sbin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/bin:/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/libexec::/sbin:/bin:/usr/sbin:/usr/bin
> SYSROOT=/usr/obj/usr/src/arm64.aarch64/tmp make
> DESTDIR=/usr/obj/usr/src/arm64.aarch64/tmp test-includes
> --- sys/abi_compat.c ---
> --- sys/acct.c ---
> --- sys/acl.c ---
> --- sys/aio.c ---
> --- 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
> sh: cannot create sys/acct.c: No such file or directory
> *** [sys/acct.c] Error code 2
>
> make[4]: stopped in /usr/src/tools/build/test-includes
> --- sys/aio.c ---
> echo "#include " > sys/aio.c
> sh: cannot create sys/aio.c: No such file or directory
> *** [sys/aio.c] Error code 2
>
> make[4]: stopped in /usr/src/tools/build/test-includes
> --- sys/acl.c ---
> echo "#include " > sys/acl.c
> sh: cannot create sys/acl.c: No such file or directory
> *** [sys/acl.c] Error code 2
>
>
> 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).
>
> I'd really like to understand why this error comes about. If someone has
> any insights, please share them :)
>
What build options are you using?  this is the test to make sure that files
can be included on their own.

Warner


Re: USB Disk Stalls on -current

2022-02-08 Thread Sean Bruno




On 2/6/22 10:14, Sean Bruno wrote:
I'm doing something "gross" with ZFS & Plex on a little Intel NUC that I 
have here at the house to provide me with a nice little NAS at home. I'm 
using 2x USB2 external disks as the mirror.


I noted that the two USB2 disks I'm using in a mirror seem to "stall" 
from time to time and its not clear to me why.


I'd like to poke further into the USB system but I'm not sure where I 
should start to see if there is something amiss with the hardware (e.g. 
the disks suck) or if FreeBSD is losing track of something during I/O 
leading to a stall/timeout.


I'm not seeing data loss or anything, I just note from time to time 
during large file transfers that the clanking/grinding sound of the 
spinning rust on my desk completely stops, the encoding of the video 
files stops (so its waiting for a read to complete) and its gets much 
quieter in my office.  :-)


sean



I think I'm going to grab one of these fancy 5-disk USB 3 enclosures I 
see on the Internet.  ;-)


Most of the consumer grade units seem to have one or more issues (no NCQ 
depth more than 1, loud/bad fans, hard to get a real JBOD mode, JBOD 
mode eats serial numbers making ID hard).


I think I settled on the TERRAMASTER D5-300 USB3.1

I'll post back results when it arrives and I get done swearing and 
cursing during the replacement.


sean




Problem compiling firefox

2022-02-08 Thread Filippo Moretti
/usr/local/bin/clang++13 -std=gnu++17 --target=wasm32-wasi 
--sysroot=/usr/local/share/wasi-sysroot -o rlbox.wasm -Wl,--export-all 
-Wl,--stack-first -Wl,-z,stack-size=262144 -Wl,--no-entry -Wl,--growable-table 
ogg_alloc.wasm ogg_bitwise.wasm ogg_framing.wasm xmlparse.wasm xmlrole.wasm 
xmltok.wasm wasm2c_sandbox_wrapper.wasm mozHunspellRLBoxSandbox.wasm 
affentry.wasm affixmgr.wasm csutil.wasm hashmgr.wasm hunspell.wasm phonet.wasm 
replist.wasm suggestmgr.wasm GraphiteExtra.wasm CmapCache.wasm Code.wasm 
Collider.wasm Decompressor.wasm Face.wasm FeatureMap.wasm FileFace.wasm 
Font.wasm GlyphCache.wasm GlyphFace.wasm Intervals.wasm Justifier.wasm 
NameTable.wasm Pass.wasm Position.wasm Segment.wasm Silf.wasm Slot.wasm 
Sparse.wasm TtfUtil.wasm UtfCodec.wasm call_machine.wasm gr_char_info.wasm 
gr_face.wasm gr_features.wasm gr_font.wasm gr_logging.wasm gr_segment.wasm 
gr_slot.wasm json.wasm RLBoxWOFF2Sandbox.wasm table_tags.wasm 
variable_length.wasm woff2_common.wasm woff2_dec.wasm woff2_out.wasm 
-lwasi-emulated-process-clockswasm-ld: error: cannot open 
/usr/local/llvm13/lib/clang/13.0.1/lib/wasi/libclang_rt.builtins-wasm32.a: No 
such file or directoryclang-13: error: linker command failed with exit code 1 
(use -v to see invocation)gmake[5]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/rules.mk:498: rlbox.wasm] 
Error 1gmake[5]: Leaving directory 
'/usr/ports/www/firefox/work/.build/security/rlbox'gmake[4]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/recurse.mk:72: 
security/rlbox/target-objects] Error 2gmake[4]: Leaving directory 
'/usr/ports/www/firefox/work/.build'gmake[3]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/recurse.mk:34: compile] Error 
2gmake[3]: Leaving directory '/usr/ports/www/firefox/work/.build'gmake[2]: *** 
[/usr/ports/www/firefox/work/firefox-97.0/config/rules.mk:352: all] Error 
2gmake[2]: Leaving directory '/usr/ports/www/firefox/work/.build'*** Error code 
1
Stop.make[1]: stopped in /usr/ports/www/firefox*** Error code 1
Stop.make: stopped in /usr/ports/www/firefox[root@sting 
/usr/ports/www/firefox]# 
This is the error I get while  attempting to update firefox from port
[root@sting /usr/ports/www/firefox]# uname -aFreeBSD sting 14.0-CURRENT FreeBSD 
14.0-CURRENT #67 heads/main-n252631-ccf50c1df9c: Tue Jan 25 22:12:38 CET 2022   
  filippo@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64
sincerelyFilippo

Re: Problem compiling firefox

2022-02-08 Thread Charlie Li

Filippo Moretti wrote:
/usr/local/bin/clang++13 -std=gnu++17 --target=wasm32-wasi 
--sysroot=/usr/local/share/wasi-sysroot -o rlbox.wasm -Wl,--export-all 
-Wl,--stack-first -Wl,-z,stack-size=262144 -Wl,--no-entry 
-Wl,--growable-table ogg_alloc.wasm ogg_bitwise.wasm ogg_framing.wasm 
xmlparse.wasm xmlrole.wasm xmltok.wasm wasm2c_sandbox_wrapper.wasm 
mozHunspellRLBoxSandbox.wasm affentry.wasm affixmgr.wasm csutil.wasm 
hashmgr.wasm hunspell.wasm phonet.wasm replist.wasm suggestmgr.wasm 
GraphiteExtra.wasm CmapCache.wasm Code.wasm Collider.wasm 
Decompressor.wasm Face.wasm FeatureMap.wasm FileFace.wasm Font.wasm 
GlyphCache.wasm GlyphFace.wasm Intervals.wasm Justifier.wasm 
NameTable.wasm Pass.wasm Position.wasm Segment.wasm Silf.wasm Slot.wasm 
Sparse.wasm TtfUtil.wasm UtfCodec.wasm call_machine.wasm 
gr_char_info.wasm gr_face.wasm gr_features.wasm gr_font.wasm 
gr_logging.wasm gr_segment.wasm gr_slot.wasm json.wasm 
RLBoxWOFF2Sandbox.wasm table_tags.wasm variable_length.wasm 
woff2_common.wasm woff2_dec.wasm woff2_out.wasm 
-lwasi-emulated-process-clocks
wasm-ld: error: cannot open 
/usr/local/llvm13/lib/clang/13.0.1/lib/wasi/libclang_rt.builtins-wasm32.a: 
No such file or directory
clang-13: error: linker command failed with exit code 1 (use -v to see 
invocation)

Caused by a version mismatch after devel/llvm13 update, try this:
https://reviews.freebsd.org/D34206

--
Charlie Li
…nope, still don't have an exit line.


OpenPGP_signature
Description: OpenPGP digital signature


Re: buildworld failed

2022-02-08 Thread Simon J. Gerraty
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
> sh: cannot create sys/acct.c: No such file or directory
> *** [sys/acct.c] Error code 2
> 
> make[4]: stopped in /usr/src/tools/build/test-includes
> --- sys/aio.c ---
> echo "#include " > sys/aio.c
> sh: cannot create sys/aio.c: No such file or directory
> *** [sys/aio.c] Error code 2
> 
> make[4]: stopped in /usr/src/tools/build/test-includes
> --- sys/acl.c ---
> echo "#include " > sys/acl.c
> sh: cannot create sys/acl.c: No such file or directory
> *** [sys/acl.c] Error code 2
> 
> 
> 
> 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 subdir does not exist.
Best bet would be to avoid the need:

diff --git a/tools/build/test-includes/Makefile 
b/tools/build/test-includes/Makefile
index 3ae39a2cb61..eb9016ecc03 100644
--- a/tools/build/test-includes/Makefile
+++ b/tools/build/test-includes/Makefile
@@ -24,11 +24,11 @@ CFLAGS.event.c= -D_WANT_KEVENT32 
-D_WANT_FREEBSD11_KEVENT
 
 .include "badfiles.inc"
 
-.for h in ${HDRS}
+.for h c in ${HDRS:@x@$x ${x:S,/,_,g:R}.c@}
 .if !${BADHDRS:M${h}}
-SRCS+= ${h:R}.c
-CLEANFILES+=${h:R}.c
-${h:R}.c:
+SRCS+= $c
+CLEANFILES+=$c
+$c:
echo "#include <$h>" > ${.TARGET}
 .endif
 .endfor

so you get:

echo "#include " > sys_abi_compat.c
echo "#include " > sys_acct.c
echo "#include " > sys_acl.c
echo "#include " > sys_aio.c
echo "#include " > sys_alq.c
echo "#include " > sys_apm.c
echo "#include " > sys_arb.c
echo "#include " > sys_asan.c
echo "#include " > sys_assym.c

etc



Re: buildworld failed

2022-02-08 Thread Warner Losh
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/build/test-includes
> > --- sys/acct.c ---
> > echo "#include " > sys/acct.c
> > sh: cannot create sys/acct.c: No such file or directory
> > *** [sys/acct.c] Error code 2
> >
> > make[4]: stopped in /usr/src/tools/build/test-includes
> > --- sys/aio.c ---
> > echo "#include " > sys/aio.c
> > sh: cannot create sys/aio.c: No such file or directory
> > *** [sys/aio.c] Error code 2
> >
> > make[4]: stopped in /usr/src/tools/build/test-includes
> > --- sys/acl.c ---
> > echo "#include " > sys/acl.c
> > sh: cannot create sys/acl.c: No such file or directory
> > *** [sys/acl.c] Error code 2
> >
> >
> >
> > 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 subdir does not exist.
>

Why does it exist for me, though? What's making it for me and not for the
OP?


> Best bet would be to avoid the need:
>

Oh, I like this and I agree. Do you want to commit, or should I do the
honors?

Warner


> diff --git a/tools/build/test-includes/Makefile
> b/tools/build/test-includes/Makefile
> index 3ae39a2cb61..eb9016ecc03 100644
> --- a/tools/build/test-includes/Makefile
> +++ b/tools/build/test-includes/Makefile
> @@ -24,11 +24,11 @@ CFLAGS.event.c= -D_WANT_KEVENT32
> -D_WANT_FREEBSD11_KEVENT
>
>  .include "badfiles.inc"
>
> -.for h in ${HDRS}
> +.for h c in ${HDRS:@x@$x ${x:S,/,_,g:R}.c@}
>  .if !${BADHDRS:M${h}}
> -SRCS+= ${h:R}.c
> -CLEANFILES+=${h:R}.c
> -${h:R}.c:
> +SRCS+= $c
> +CLEANFILES+=$c
> +$c:
> echo "#include <$h>" > ${.TARGET}
>  .endif
>  .endfor
>
> so you get:
>
> echo "#include " > sys_abi_compat.c
> echo "#include " > sys_acct.c
> echo "#include " > sys_acl.c
> echo "#include " > sys_aio.c
> echo "#include " > sys_alq.c
> echo "#include " > sys_apm.c
> echo "#include " > sys_arb.c
> echo "#include " > sys_asan.c
> echo "#include " > sys_assym.c
>
> etc
>


Re: buildworld failed

2022-02-08 Thread Brooks Davis
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/src/tools/build/test-includes
> > --- sys/acct.c ---
> > echo "#include " > sys/acct.c
> > sh: cannot create sys/acct.c: No such file or directory
> > *** [sys/acct.c] Error code 2
> > 
> > make[4]: stopped in /usr/src/tools/build/test-includes
> > --- sys/aio.c ---
> > echo "#include " > sys/aio.c
> > sh: cannot create sys/aio.c: No such file or directory
> > *** [sys/aio.c] Error code 2
> > 
> > make[4]: stopped in /usr/src/tools/build/test-includes
> > --- sys/acl.c ---
> > echo "#include " > sys/acl.c
> > sh: cannot create sys/acl.c: No such file or directory
> > *** [sys/acl.c] Error code 2
> > 
> > 
> > 
> > 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 subdir does not exist.
> Best bet would be to avoid the need:
> 
> diff --git a/tools/build/test-includes/Makefile 
> b/tools/build/test-includes/Makefile
> index 3ae39a2cb61..eb9016ecc03 100644
> --- a/tools/build/test-includes/Makefile
> +++ b/tools/build/test-includes/Makefile
> @@ -24,11 +24,11 @@ CFLAGS.event.c=   -D_WANT_KEVENT32 
> -D_WANT_FREEBSD11_KEVENT
>  
>  .include "badfiles.inc"
>  
> -.for h in ${HDRS}
> +.for h c in ${HDRS:@x@$x ${x:S,/,_,g:R}.c@}
>  .if !${BADHDRS:M${h}}
> -SRCS+=   ${h:R}.c
> -CLEANFILES+=${h:R}.c
> -${h:R}.c:
> +SRCS+=   $c
> +CLEANFILES+=$c
> +$c:
>   echo "#include <$h>" > ${.TARGET}
>  .endif
>  .endfor
> 
> so you get:
> 
> echo "#include " > sys_abi_compat.c
> echo "#include " > sys_acct.c
> echo "#include " > sys_acl.c
> echo "#include " > sys_aio.c
> echo "#include " > sys_alq.c
> echo "#include " > sys_apm.c
> echo "#include " > sys_arb.c
> echo "#include " > sys_asan.c
> echo "#include " > sys_assym.c
> 
> etc
> 

This would be fine, but should not be necessicary. The sys subdir should
be created by AUTOOBJ.

-- Brooks


signature.asc
Description: PGP signature


Re: buildworld failed

2022-02-08 Thread Simon J. Gerraty
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 subdir does not exist.
> 
> Why does it exist for me, though? What's making it for me and not for the OP?

Unless you cleaned your tree recently, that could just be an artifact of
an earlier version of the makefile.

> 
> Best bet would be to avoid the need:
> 
> Oh, I like this and I agree. Do you want to commit, or should I do the honors?

Feel free, I've got my hands full at present.



Panic, CURRENT, yesterday

2022-02-08 Thread Larry Rosenman

I got the following last night while doing a poudriere run as well as
a full bacula backup:

borg.lerctr.org dumped core - see /var/crash/vmcore.0

Mon Feb  7 23:05:48 CST 2022

FreeBSD borg.lerctr.org 14.0-CURRENT FreeBSD 14.0-CURRENT #54 
ler/freebsd-main-changes-n252969-5e5fd0c788c: Sat Feb  5 14:48:30 CST 
2022 
r...@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL  amd64


panic: ng_snd_item: 42 != 290

GNU gdb (GDB) 11.2 [GDB v11.2 for FreeBSD]
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd14.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...
Reading symbols from /usr/lib/debug//boot/kernel/kernel.debug...

Unread portion of the kernel message buffer:
panic: ng_snd_item: 42 != 290
cpuid = 0
time = 1644295724
KDB: stack backtrace:
#0 0x80515fc5 at kdb_backtrace+0x65
#1 0x804cbaef at vpanic+0x17f
#2 0x804cb8c3 at panic+0x43
#3 0x82c765b7 at ng_snd_item+0x587
#4 0x82c8f263 at ng_ether_output+0xb3
#5 0x805e0c1d at ether_output+0x6cd
#6 0x805f6251 at arpintr+0xd71
#7 0x805e5587 at netisr_dispatch_src+0x97
#8 0x805e0f1e at ether_demux+0x14e
#9 0x82c8f89c at ng_ether_rcv_upper+0x12c
#10 0x82c76dab at ng_apply_item+0x7eb
#11 0x82c7638d at ng_snd_item+0x35d
#12 0x82c76dab at ng_apply_item+0x7eb
#13 0x82c7638d at ng_snd_item+0x35d
#14 0x82c8f33f at ng_ether_input+0x9f
#15 0x805e21d7 at ether_nh_input+0x217
#16 0x805e5587 at netisr_dispatch_src+0x97
#17 0x805e138d at ether_input+0x5d
Uptime: 2d7h20m52s
Dumping 28321 out of 131023 
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%


__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
55  __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" 
(offsetof(struct pcpu,

(kgdb) #0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1  doadump (textdump=)
at /usr/src/sys/kern/kern_shutdown.c:399
#2  0x804cb6ff in kern_reboot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:487
#3  0x804cbb5e in vpanic (fmt=0x82c7fd98 "%s: %d != %d",
ap=) at /usr/src/sys/kern/kern_shutdown.c:920
#4  0x804cb8c3 in panic (fmt=)
at /usr/src/sys/kern/kern_shutdown.c:844
#5  0x82c765b7 in ng_snd_item (item=0xf8116a9f3900, flags=0)
at /usr/src/sys/netgraph/ng_base.c:2256
#6  0x82c8f263 in ng_ether_output (ifp=,
ifp@entry=,
mp=0xfe025a5b2868,
mp@entry=)
at /usr/src/sys/netgraph/ng_ether.c:294
#7  0x805e0c1d in ether_output (ifp=0xf8010dc57000,
m=0xf81736a3f600, dst=, ro=)
at /usr/src/sys/net/if_ethersubr.c:427
#8  0x805f6251 in in_arpinput (m=0xf81736a3f600)
at /usr/src/sys/netinet/if_ether.c:1129
#9  arpintr (m=0xf81736a3f600,
m@entry=)
at /usr/src/sys/netinet/if_ether.c:739
#10 0x805e5587 in netisr_dispatch_src (proto=4,
source=source@entry=0, m=0xf81736a3f600)
at /usr/src/sys/net/netisr.c:1153
#11 0x805e58df in netisr_dispatch (proto=,
m=) at /usr/src/sys/net/netisr.c:1244
#12 0x805e0f1e in ether_demux (ifp=ifp@entry=0xf8010dc57000,
m=, m@entry=0xf81736a3f600)
at /usr/src/sys/net/if_ethersubr.c:926
#13 0x82c8f89c in ng_ether_rcv_upper (hook=,
hook@entry=,
item=0xf8116a9f3900,
item@entry=)
at /usr/src/sys/netgraph/ng_ether.c:742
#14 0x82c76dab in ng_apply_item 
(node=node@entry=0xf8018a9b8c00,

item=item@entry=0xf8116a9f3900, rw=0)
at /usr/src/sys/netgraph/ng_base.c:2406
#15 0x82c7638d in ng_snd_item (item=0xf8116a9f3900,
item@entry=, 
flags=0,

flags@entry=)
at /usr/src/sys/netgraph/ng_base.c:2323
#16 0x82c76dab in ng_apply_item 
(node=node@entry=0xf8115dd94300,

item=item@entry=0xf8116a9f3900, rw=0)
at /usr/src/sys/netgraph/ng_base.c:2406
#17 0x82c7638d in ng_snd_item 
(item=item@entry=0xf8116a9f3900,

flags=flags@entry=0) at /usr/src/sys/netgraph/ng_base.c:2323
#18 0x82c8f33f in ng_ether_input (ifp=,
ifp@entry=,
mp=0xfe025a5b2cf8,
mp@entry=)
at /usr/src/sys/netgraph/ng_ether.c:255
#19 0x805e21d7 in ether_input_internal (ifp=0xf8010dc57000,
m=0xf81736a3f600) at /usr/src/sys/net/if_ethersubr.c:661
#20 ether_nh_input (

Re: buildworld failed

2022-02-08 Thread Simon J. Gerraty
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 replacing / with
_ is simpler.




Re: buildworld failed

2022-02-08 Thread Warner Losh
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 the problem,
> but given the nature of what the makefile is doing just replacing / with
> _ is simpler.
>

Agreed. Testing this.

Warner


Re: buildworld failed

2022-02-08 Thread Warner Losh
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 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 replacing / with
>> _ is simpler.
>>
>
> Agreed. Testing this.
>
> Warner
>


Re: buildworld failed

2022-02-08 Thread Brooks Davis
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 2015
(cee9be4971a56f2a748eb78df97b72e42fe860ab).  If this is broken if some
supported modes we should fix it or remove it (but I belive clang/llvm
depends on it).

-- Brooks


signature.asc
Description: PGP signature


Re: buildworld failed

2022-02-08 Thread Simon J. Gerraty
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 support for relative paths in SRCS since 2015
> (cee9be4971a56f2a748eb78df97b72e42fe860ab).  If this is broken if some
> supported modes we should fix it or remove it (but I belive clang/llvm
> depends on it).

That logic appears to be in bsd.obj.mk as part of the obj target
it depends on SRCS containing paths with /

That target does not get run if one is using auto.obj.mk

--sjg