Search Criteria
Package Details: vfstool-git 2.5.r2.gad0a7c3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/vfstool-git.git (read-only, click to copy) |
|---|---|
| Package Base: | vfstool-git |
| Description: | Application for OpenMW modlists designed to allow introspecting into and creating virtual filesystems, even for other games. |
| Upstream URL: | https://github.com/DreamWeave-MP/vfstool |
| Licenses: | GPL |
| Provides: | vfstool |
| Submitter: | S3ctor |
| Maintainer: | S3ctor |
| Last Packager: | S3ctor |
| Votes: | 2 |
| Popularity: | 0.121102 |
| First Submitted: | 2025-04-25 04:32 (UTC) |
| Last Updated: | 2026-01-13 19:45 (UTC) |
Dependencies (2)
- cargo (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rust, rustup) (make)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
Latest Comments
Spaicrab commented on 2026-04-23 16:20 (UTC) (edited on 2026-04-23 16:21 (UTC) by Spaicrab)
This fails the package() step because of line 45 in the PKGBUILD:
install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"There is no singular LICENSE file, instead there are two different license files: LICENSE-APACHE and LICENSE-MIT. Editing line 45 to copy one or both of them should fix the issue.
Kovariszt commented on 2026-02-05 17:21 (UTC)
Yes,
options=('!lto')also fixes it for me. Very odd, I wonder what that's aboutEngdyn commented on 2026-02-05 07:59 (UTC)
Adding
options=('!lto')does fix it consistently for me. It's a known thing that rust + lto + arch build system do have very weird interactionsKovariszt commented on 2026-02-05 01:03 (UTC)
delta-plugin-gitbuilds without any issues for me, for some reasonS3ctor commented on 2026-02-05 00:54 (UTC)
Kovariszt, could you please do me a favor and see if
delta-plugin-gitbuilds for you? These two both have the same lz4 link error, and in my chroot, I was able to build delta-plugin after applying the relevant changes. I'll give it a try here though.Kovariszt commented on 2026-02-05 00:50 (UTC)
I'm still having the exact same issue as the previous people did, the fix doesn't seem to actually have fixed it
S3ctor commented on 2026-01-18 17:53 (UTC)
Hey, everyone. I apologize for the delay in fixing this package! I pushed a fix a few days ago that should work. In the check phase, tests also need to be built in release mode or that triggers the lz4 link error.
I tried to investigate it a bit and I'm honestly not entirely sure what the issue is. I think it may be a bug in lzzz, which vfstool_lib inherits from the ba2 crate. lzzz vendors the LZ4 library, so as far as I understand it should build and link properly either way, but, I didn't look at its build.rs especially closely once I got that far down.
Engdyn commented on 2025-12-21 01:09 (UTC)
I looked into it and has something to do with lto. Removing lto flags fixed it for me. It also seems that the llz4 linker flag isn't needed anymore
toynbeeidea commented on 2025-12-20 23:56 (UTC) (edited on 2025-12-20 23:57 (UTC) by toynbeeidea)
Build still fails:
[snip]
Engdyn commented on 2025-07-10 15:58 (UTC)
The build fails in a clean chroot with a linker error.
Adding
export RUSTFLAGS+=" -C link-arg=-llz4into build() resolves the issue.Also the license is wrong. You are using MIT not GPL in your upstream git repo. The pkg should also install the license of the upstream repo.
install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"