Package Details: trunk 0.21.6-1

Git Clone URL: https://aur.archlinux.org/trunk.git (read-only, click to copy)
Package Base: trunk
Description: Build, bundle & ship your Rust WASM application to the web.
Upstream URL: https://github.com/thedodd/trunk/
Licenses: MIT, Apache
Submitter: greyltc
Maintainer: Sanpi
Last Packager: Sanpi
Votes: 7
Popularity: 0.012949
First Submitted: 2021-01-09 13:56 (UTC)
Last Updated: 2025-01-20 13:35 (UTC)

Latest Comments

Sanpi commented on 2024-04-11 17:26 (UTC)

I reproduced the error with the latest release. I disabled lto in the PKGBUILD. Thank you @jonasmalacofilho.

jonasmalacofilho commented on 2024-02-10 12:25 (UTC)

Had to add options=(!lto) to successfully link trunk due to https://github.com/briansmith/ring/issues/1444, having Rust LTO enabled in my ~/.cargo/config.toml, and (Arch's default) GCC LTO enabled in /etc/makepkg.conf.

@graysky, I'm guessing this is the issue you have as well.

graysky commented on 2024-01-13 12:41 (UTC)

Build failure for me. Others?

...
   Compiling reqwest v0.11.22
   Compiling trunk v0.18.4 (/build/trunk/src/trunk-0.18.4)
error: linking with `cc` failed: exit status: 1
...

jonasmalacofilho commented on 2023-12-17 18:15 (UTC)

I saw that in trunk#581 thedodd says that Cargo.lock gets out of date anytime a release is minted, but that's odd.

I don't remember seeing anything in the Cargo docs that might suggest that's the case, and this also appears to be the only bin crate (I use) that requires disabling --locked.

Not to mention the fact that it used to build just fine with --locked up to (and including) 17.2.

Sanpi commented on 2022-08-08 14:21 (UTC)

@mhutter You can skip the tests by running makepkg --nocheck

mhutter commented on 2022-08-08 14:16 (UTC)

This will run the tests on each install, which adds an additional 2-3min of build time (on an 8-core CPU), is this intended? If so, what's the reasoning behind it?