Search Criteria
Package Details: minidump-stackwalk 0.19.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/minidump-stackwalk.git (read-only, click to copy) |
|---|---|
| Package Base: | minidump-stackwalk |
| Description: | A CLI minidump analyzer |
| Upstream URL: | https://crates.io/crates/minidump-stackwalk |
| Licenses: | MIT |
| Submitter: | dbrgn |
| Maintainer: | dbrgn |
| Last Packager: | dbrgn |
| Votes: | 1 |
| Popularity: | 0.000378 |
| First Submitted: | 2022-07-12 16:14 (UTC) |
| Last Updated: | 2023-11-15 22:48 (UTC) |
Dependencies (3)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rust, rustup) (make)
- rust (rust-nightlyAUR, rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup) (make)
Latest Comments
dbrgn commented on 2023-11-15 22:48 (UTC)
@bionade24: Ah, I wasn't yet aware of those helper scripts. Nice!
I can confirm that disabling LTO via options seems to resolve the issue. I updated the PKGBUILD. (Additionally, the missing custom license is fixed, and I bumped the package to version 0.19.1.)
bionade24 commented on 2023-11-13 21:28 (UTC) (edited on 2023-11-13 21:29 (UTC) by bionade24)
@dbrgn: I used the official
extra-x86_64-buildscript (see the cmd in the beginning) which uses themakepkg.confprovided under/usr/share/devtools, which has lto enabled. The default/etc/makepkg.confhas lto disabled, explaining the build problem. May you please disable the lto option in the PKGBUILD explicitly, as that would be the right way to do it? https://man.archlinux.org/man/PKGBUILD.5#OPTIONS_AND_DIRECTIVESdbrgn commented on 2023-11-13 09:21 (UTC)
@bionade24: I cannot reproduce this issue. I started a clean Docker container with the "archlinux" image, installed "base-devel", added a non-root user, downloaded the .tar.gz for this AUR package, and successfully built the package with "makepkg -sfi".
How do you set up your chroot? Do you do any cross compilation? From reading the stack trace, it seems to be a linking issue, maybe related to LTO? https://github.com/briansmith/ring/issues/1444
In any case, it's definitely an issue related to the "ring" library. Maybe the issue tracker helps with tracking down the root cause.
bionade24 commented on 2023-11-11 11:46 (UTC)
Does not build in a clean chroot: https://bpa.st/Z2MEQ7R2KYDHKU2LL6GMHF7N44