o/

anyone recognize this coredump? dpaste.com/996JFRWYV

this is on a 13.4 stable from last week ish but I see an old issue with a similar looking panic bugs.freebsd.org/bugzilla/show_bug.cgi?id=225528

Anyone using sanoid and syncoid on FreeBSD? They are respectively ZFS Snapshot management tools and remote upload tools

I hear many good things about it but then I see stuff like this: github.com/jimsalterjrs/sanoid/blob/master/FREEBSD.readme

"Please change your root shell and make symlinks in paths", doesn't sound like very well made software :/

So I'm not really sure whether it's worth the hassle

And if the changing of the root shell has side-effects

ugen2.2: <Realtek USB 10/100/1G/2.5G LAN> at usbus2 <- how to use this as CDC-NCM device?

# usbconfig -d ugen2.2 set_config 1

cdce0 on uhub1

cdce0: <Realtek USB 10/100/1G/2.5G LAN, class 0/0, rev 3.20/31.00, addr 1> on usbus2

hmm

ah, it's if_ure...

Realtek USB lan if, because bad * bad = probably good :D

Is #freebsd-pulse dead or is it just my IRC client acting up?

the bot left some time ago

geezabiscuit: ^^^

Ah, thanks.

Is there a way to install vscode in FreeBSD?

I know that I can compile vscode but it asks for configuring options very frequently so I can't just leave the computer compiling for night

ghodawalaaman: It should be available as a pkg

$ pkg search vscode / vscode-1.96.2 Visual Studio Code - Open Source ("Code - OSS")

vkarlsen: yeah, I checked last time it wasn't available

Thanks

ghodawalaaman, only MS could fuck-up a build process like that.

Though I guess you could build it in a screen session and just check on it every now and again.

Or script something that texted or E-mailed you when CPU usage dropped.

Prolly both, actually.

yeah, I could try these.

surely the freebsd have already figured something out, no need to speculate :O

s/the freebsd/& packagers/

stuff like that just isn't an issue for me

With the AI integration in Warp I can just run the command and let the AI interact with it, based on the instructions i provide for it at the start

You can avoid paused builds asking for options by doing 'make config-recursive' before starting the build. Just keep in mind your choices can pull in more dependencies with their own options, so repeat until it stops asking.

If you want default options all the way down, start it off with 'make -DBATCH'

wildeboskat: the default shell is sh now

yes, but that's only a mild regression

ah ok I didn't notice, I normally use zsh

but it does seem very linux centric, i probably wouldn't bother with it

wildeboskat: I've used sanoid and syncoid on FreeBSD since before the default shell got changed. I used the toor user instead of root. But nowadays, with root using /bin/sh this isn't a problem

Huh that's a good idea

Making another user with uid 0

i don't recall ever having to fiddle with symlinking perl. been using sanoid/syncoid close to 1.5 years now, before the release of 14.0-RELEASE. hm

The port takes care of the shebang to /usr/local/bin/perl, this becomes an issue only if you install it outside of ports/pkgs

I still have root's shell set to csh in some places, because I haven't seen a good reason to change it

Ohhh there is a port

I didn't realise

It looks like a great option, a bit like Apple timemachine

Except not on an external volume of course

But that's where syncoid can come in

Besides, I do a full image every month or so

Hi, I compiled a library on FreeBSD 13.1 that uses libhwy.so.1 and raises this error when loading: '/usr/local/lib/libhwy.so.1: Undefined symbol \"_ZNSt3__122__libcpp_verbose_abortEPKcz\"'".

The library I'm compiling is called vix: github.com/akash-akya/vix

It builds ok, but I get this error when the Erlang runtime tries to load.

Does anyone know if it's possible to avoid that "_libcpp_verbose_abort" error?

well you avoid that by linking the library with that symbol

releases.llvm.org/16.0.0/projects/libcxx/docs/UsingLibcxx.html i suspect the makefile for hwy creates a file with that function

when i'm using ocaml with opam to build/install packages, i occasionally need to prefix my `opam install` command with `C_INCLUDE_PATH=$C_INCLUDE_PATH:/usr/local/include` and/or `CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:usr/local/include` and/or `LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib` .. i wouldn't be surprised to hear that's needed there as well

scoobybejesus: let's try that

`C_INCLUDE_PATH=$C_INCLUDE_PATH:/usr/local/include CPLUS_INCLUDE_PATH=$CPLUS_INCLUDE_PATH:usr/local/include LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib opam install liquidsoap` for example

Mmm, no, same issue

Btw, this is compiled with clang 13.0.0

Mm, it looks like the issue is related to something else. When I try to install a dependency (libvips) I get this error: g_module_open() failed for /usr/local/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jxl.so: /usr/local/lib/libjxl.so.0.11: Undefined symbol "_ZNSt3__122__libcpp_verbose_abortEPKcz"

upgrading packages before trying again...

that seems like an old clang

elliot@phil:~/$ cc -v

FreeBSD clang version 18.1.5 (github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9)

rtprio: this is a FreeBSD 13.1, clang version 13.0.0

I need this version because the target platform is a jail running on TrueNAS Core that as far as I understand it supports FreeBSD 13.1

martinrame: You can update TrueNAS to the latest 13.3-U1 and update your jails to 13.4, if you'd like.

ek: thanks. First I'll create a new 13.3 jail in the dev machine to see if this builds, then copy to TrueNAS.

martinrame: Okey dokey. In 13.4 you'll at least get clang 18.1.6.

ek: let's try 13.4, then!.

martinrame: Likely your best bet. You may also need to make some adjustments to your compilation options. That's only a maybe, though, as I'm not familiar with the software or what it requires to successfully build and run on FBSD.