Package Details: linux-bcachefs-git 6.15.0.rc4.1.bcachefs.git.00259.g17227e8eaf3b-1

Git Clone URL: https://aur.archlinux.org/linux-bcachefs-git.git (read-only, click to copy)
Package Base: linux-bcachefs-git
Description: The Linux kernel and modules ~ featuring Kent Overstreet's bcachefs filesystem
Upstream URL: https://github.com/koverstreet/bcachefs
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: Chiruno
Maintainer: QuartzDragon
Last Packager: QuartzDragon
Votes: 16
Popularity: 0.000005
First Submitted: 2018-01-13 15:37 (UTC)
Last Updated: 2025-05-22 01:21 (UTC)

Required by (6)

Sources (2)

Pinned Comments

QuartzDragon commented on 2019-06-11 15:15 (UTC) (edited on 2019-06-11 15:17 (UTC) by QuartzDragon)

If there are bugs related to the PKGBUILD or config, report here.

Otherwise, please report here:

https://github.com/koverstreet/bcachefs/issues

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »

QuartzDragon commented on 2023-07-12 09:32 (UTC)

@CatMatrix

That's not the actual error. The actual error will be lost in the mix of compilation output. I would suggest piping the output of makepkg to a text file, and the searching for "error" to find the actual error message.

CatMatrix commented on 2023-07-12 09:20 (UTC)

@QuartzDragon I edited my comments and it looks like they were in different places with the same error

QuartzDragon commented on 2023-07-12 09:14 (UTC)

@CatMatrix

Post it anyways, so there's somewhere to start.

CatMatrix commented on 2023-07-12 07:22 (UTC) (edited on 2023-07-12 09:17 (UTC) by CatMatrix)

@QuartzDragon I imported export LC_ALL=C and recompiled, this time the error is not the same as last time

  CC [M]  drivers/gpu/drm/nouveau/nv84_fence.o
  CC [M]  drivers/gpu/drm/nouveau/nvc0_fence.o
  LD [M]  drivers/gpu/drm/nouveau/nouveau.o
  AR      drivers/gpu/built-in.a
make[1]: *** [scripts/Makefile.build:494:drivers] Error 2
make: *** [Makefile:2026:.] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'linux-bcachefs-git-6.4.2.arch1.r1189887.924149fbe383-1 (linux-bcachefs-git linux-bcachefs-git-headers)':

QuartzDragon commented on 2023-07-12 06:57 (UTC)

@CatMatrix

Please try recompling and reposting error after running export LC_ALL=C. It will output English error messages.

CatMatrix commented on 2023-07-12 04:27 (UTC) (edited on 2023-07-12 07:20 (UTC) by CatMatrix)

I can't compile the package, it returns the following error message

  CC [M]  drivers/net/usb/ipheth.o
  CC [M]  drivers/net/usb/sierra_net.o
  CC [M]  drivers/net/usb/cx82310_eth.o
  CC [M]  drivers/net/usb/cdc_ncm.o
  CC [M]  drivers/net/usb/huawei_cdc_ncm.o
  CC [M]  drivers/net/usb/lg-vl600.o
  CC [M]  drivers/net/usb/qmi_wwan.o
  CC [M]  drivers/net/usb/cdc_mbim.o
  CC [M]  drivers/net/usb/ch9200.o
  CC [M]  drivers/net/usb/aqc111.o
  CC [M]  drivers/net/usb/r8153_ecm.o
  LD [M]  drivers/net/usb/asix.o
make[1]: *** [scripts/Makefile.build:494:drivers] Error 2
make: *** [Makefile:2026: .] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'linux-bcachefs-git-6.4.2.arch1.r1189887.924149fbe383-1 (linux-bcachefs-git linux-bcachefs-git-headers)':

I tried compiling on a different machine and got the same error, deleting the repo and re-downloading didn't work And I didn't find a file for "scripts/Makefile.build" either. Any help would be greatly appreciated.

(English is not my native language; please excuse typing errors.)

QuartzDragon commented on 2023-06-29 12:55 (UTC)

@Nanoshift

Don't know, sorry. It's part of the same make process that builds the kernel, so it is probably some upstream bug. I can't fix something like that.

Nanoshift commented on 2023-05-23 22:12 (UTC) (edited on 2023-05-23 22:13 (UTC) by Nanoshift)

The docs take a long time to build on my system due to sphinx-build using -j1 on my 16-thread system. Is there a way to change that? Edit: MAKEFLAGS="-j16" doesn't change it.

QuartzDragon commented on 2023-05-12 06:40 (UTC)

@Nanoshift

Should be fixed now