@kkiyama117
Please post your output by running it with LANG=C
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) |
« First ‹ Previous 1 2 3 4 5 6 7 .. 14 Next › Last »
@kkiyama117
Please post your output by running it with LANG=C
@QuartzDragon @snogard
I got the same error message (which occurred when I called paru -S linux-bcachefs-git
).
Can I do anything in my environment to debug this error and identify a solution for people who get this error (including me)?
The error message was as follows (I am Japanese and set LANG=JA_JP, so some output is in Japanese, but the error message is the same as reported by @snogard).
...
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
-> Prepared linux-bcachefs-git version 6.7.0-rc4-1-bcachefs-git-00093-ge640951db2f7-dirty
==> pkgver() を開始...
==> 更新されたバージョン: linux-bcachefs-git 6.7.0.rc4.1.bcachefs.git.00093.ge640951db2f7.dirty-1
==> ソースの準備ができました。
linux-bcachefs-git-6.7.0.rc4.1.bcachefs.git.00088.g7b9c2240f97d.dirty-1: パッケージリストを解析しています...
==> パッケージを作成: linux-bcachefs-git 6.7.0.rc4.1.bcachefs.git.00093.ge640951db2f7.dirty-1 (2023年12月06日 09時35分46秒)
==> ランタイムの依存関係を確認...
==> ビルドタイムの依存関係を確認...
==> 警告: 既存の $srcdir/ ツリーを使用
==> pkgver() を開始...
==> エラー: pkgver を空にすることはできません。
==> エラー: pkgver() が不正なバージョンを生成しました:
エラー: 'linux-bcachefs-git-6.7.0.rc4.1.bcachefs.git.00088.g7b9c2240f97d.dirty-1' のビルドに失敗しました:
エラー: パッケージのビルドに失敗しました: linux-bcachefs-git-6.7.0.rc4.1.bcachefs.git.00088.g7b9c2240f97d.dirty-1
@snogard
Cannot reproduce here. Make sure that the package Git repo is updated, and that the PKGBUILD hasn't been altered.
Perhaps delete sources, because they might possibly be corrupted on your end.
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version:
error: failed to build 'linux-bcachefs-git-6.7.0.rc2.1.bcachefs.git.00102.gc80a1d564930.dirty-1 (linux-bcachefs-git linux-bcachefs-git-headers)'
@demizer
Thankfully, yeah.
Seems the update on 9-03 fixed the missing symbols issue.
Issue for the build failures regarding the missing symbols as reported in comments
reported upstream here: https://github.com/koverstreet/bcachefs/issues/590
@ticpu
Please report upstream if you haven't already.
Shouldn't have to work around stuff in config... but when even that doesn't work... with a filesystem have little knowledge about the inner workings of, I find it far safer to just leave things to Kent or the others working on bcachefs to resolve, and so present fixes for.
I guess I don't want to be responsible for creating weird bugs that might eat people's data, heh.
The latest version gives me the same issue as shintak but enabling CONFIG_LOCK_STAT didn't fix it. I had to remove the 2 tracepoints in the code to finish compiling.
diff --git a/fs/bcachefs/six.c b/fs/bcachefs/six.c
index 581aee565e95..4fce655a94e9 100644
--- a/fs/bcachefs/six.c
+++ b/fs/bcachefs/six.c
@@ -456,7 +456,6 @@ static int six_lock_slowpath(struct six_lock *lock, enum six_lock_type type,
smp_mb__after_atomic();
}
- trace_contention_begin(lock, 0);
lock_contended(&lock->dep_map, ip);
if (six_optimistic_spin(lock, type))
@@ -526,7 +525,6 @@ static int six_lock_slowpath(struct six_lock *lock, enum six_lock_type type,
six_clear_bitmask(lock, SIX_LOCK_HELD_write);
six_lock_wakeup(lock, atomic_read(&lock->state), SIX_LOCK_read);
}
- trace_contention_end(lock, 0);
return ret;
}
@shintak
Please report this upstream as soon as possible, as it will help immensely with Kent fixing these sort of bugs.
Enabling CONFIG_LOCK_STAT bloats the install size quite a bit... not sure whether to actually enable it, or just wait until Kent fixes said bug.
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