Search Criteria
Package Details: tirith 0.3.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/tirith.git (read-only, click to copy) |
|---|---|
| Package Base: | tirith |
| Description: | Terminal security - catches homograph attacks, pipe-to-shell, ANSI injection |
| Upstream URL: | https://github.com/sheeki03/tirith |
| Licenses: | AGPL-3.0-only |
| Submitter: | sheeki |
| Maintainer: | sheeki |
| Last Packager: | sheeki |
| Votes: | 6 |
| Popularity: | 0.64 |
| First Submitted: | 2026-02-03 12:11 (UTC) |
| Last Updated: | 2026-06-19 06:07 (UTC) |
Dependencies (3)
- gcc-libs (gcc-libs-gitAUR, gcc-libs-fast-optimizedAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- base-devel (make)
- cargo (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rust, rustup) (make)
Latest Comments
zerojay commented on 2026-02-14 02:09 (UTC)
Sure, I don't mind testing the PKGBUILD.
sheeki commented on 2026-02-13 18:43 (UTC)
I’ve hardened the PKGBUILD so linker config is forced at build time: it now pins the Rust target linker to gcc and forces GNU bfd backend, which avoids lld-related ring link failures even when local defaults are unusual. This will ship in the next release along with other new features and improvements early next week
meanwhile If you want the fix before release, reply here and I’ll share a test PKGBUILD/commit you can build immediately. If it still fails after that, please include: - full
makepkgbuild log -rustc -vV-gcc --version-ld --versionzerojay commented on 2026-02-13 18:11 (UTC)
Hi, I am getting the exact same error message as mozzi32 even with the workaround listed, I get the same error. I do not have a custom linker setup that I am aware of as I have no ~/.cargo/config.toml at all.
sheeki commented on 2026-02-09 15:00 (UTC)
This is a linker compatibility issue on your system. The
ringcrate, which is a cryptography dependency, can fail to link whenlldis set as the default linker instead of GNUld.For now, you can build the package with:
RUSTFLAGS="-Clinker=gcc" makepkg -si
If that doesn’t work, please check whether you have a custom linker configured in
~/.cargo/config.toml.I’ve hardened the PKGBUILD for the next release so this issue won’t occur regardless of the user's linker configuration. Let me know if you’re still running into problems.
mozzi32 commented on 2026-02-09 14:53 (UTC)
Doesn't work :
"ld.lld: error: too many errors emitted, stopping now (use --error-limit=0 to see all errors) collect2: error: ld returned 1 exit status
error: could not compile
tirith(bin "tirith") due to 1 previous error ==> ERREUR : Une erreur s’est produite dans build(). Abandon… :: Unable to build tirith - makepkg exited with code: 4"