Building in a clean chroot fails with

Package libudev was not found in the pkg-config search path.
Perhaps you should add the directory containing `libudev.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libudev', required by 'virtual:world', not found
Makefile:52: *** pkg-config error, command: pkg-config --cflags "blkid uuid liburcu libsodium zlib liblz4 libzstd libudev".  Stop.

IS there any reason for adding cargo into makedepends? The package successfully works without it.

@QuartzDragon no segfault with running bcachefs format. maybe it got fixed? also, need to add cargo and clang build dependencies with version 580.

@abelian424

According to the GCC manpage, -O is equivalent to -O1.

-O0 does zero optimizations, I think.

I did that, because it fixed whatever bug @Vitruvius was having.

If I were you, I'd test to see if -O1 produces a segfault or not with running bcachefs format <disk>.

If not, I'll update the PKGBUILD defaults.

Otherwise, you're more than free to change that line to suit your own needs.

Shouldn't this be built with EXTRA_CFLAGS="-O" instead of EXTRA_CFLAGS="-O0"? It seems to build fine, and I don't get warnings about fortify build.

When running mkinitcpio I get

==> ERROR: module not found: `bcachefs'
==> ERROR: binary dependency `libaio.so.1' not found for `bcachefs'

I think libaio needs to be moved from a makedep to a dep.

@misson20000

Tell me if the latest update fixed it.

I get errors from mkinitcpio about not finding the "bcachefs:" module. I suspect this comes from erroneous use of backticks on line 44 of add-mkinitcpio-hook-for-Arch.patch, which expands to "bcachefs: missing command".

I believe build dependencies on fuse3 and valgrind are missing.

Totally bizarre bug; I'm dropping a comment here in case it helps anyone else: The default optimization level (-O2) caused a segfault when running bcachefs format <disk>. Building with EXTRA_CFLAGS="-O0" fixed it.