Search Criteria
Package Details: libbacktrace-git r73.ad106d5-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/libbacktrace-git.git (read-only, click to copy) |
---|---|
Package Base: | libbacktrace-git |
Description: | Library to produce symbolic backtraces |
Upstream URL: | https://github.com/ianlancetaylor/libbacktrace |
Licenses: | BSD |
Conflicts: | libbacktrace |
Provides: | libbacktrace, libbacktrace.so |
Submitter: | Chocobo1 |
Maintainer: | Chocobo1 |
Last Packager: | Chocobo1 |
Votes: | 7 |
Popularity: | 0.25 |
First Submitted: | 2019-04-16 04:00 (UTC) |
Last Updated: | 2023-02-10 03:27 (UTC) |
Dependencies (4)
- gcc-libs (gccrs-libs-git, gcc-libs-git)
- zlib (zlib-static, zlib-ng-compat-git, zlib-git, zlib-ng-compat)
- git (git-vfs, git-git, git-run-command-patch-git) (make)
- libunwind (libunwind-git, libunwind-carbon) (make)
Required by (13)
- axecore
- boost-stacktrace-backtrace
- dash-cli
- dash-daemon
- dash-qt
- dashcore
- dashcore-git
- dhewm3-git (requires libbacktrace.so)
- dhewm3-git (requires libbacktrace) (make)
- dv-processing
- extension-manager
- extension-manager-git
- zrythm (requires libbacktrace)
Latest Comments
1 2 Next › Last »
Chocobo1 commented on 2023-02-10 03:30 (UTC)
Seems makepkg doesn't remove unrelated files from the repository before building. Anyway I have temporarily patched it so it won't fail for now.
yochananmarqos commented on 2023-02-09 21:29 (UTC)
@zed123: The
0002-Add-pkg-config-file.patch
is no longer needed as it was taken care of upstream.My PKGBUILD
zed123 commented on 2023-02-09 20:46 (UTC)
Cannot build package:
==> Starting prepare()... patching file configure.ac patching file Makefile.am Hunk #1 succeeded at 84 with fuzz 1. patching file configure.ac Hunk #1 succeeded at 568 (offset 30 lines). The next patch would create the file libbacktrace.pc.in, which already exists! Skipping patch. 1 out of 1 hunk ignored ==> ERROR: A failure occurred in prepare(). Aborting...
Command 'makepkg' failed to execute.
abouvier commented on 2022-12-08 18:24 (UTC)
I believe it's because it slows down the compilation when LTO is enabled, but is only useful when packages contain static libraries.
Also this option is ignored when LTO is disabled, so there is no harm in adding it when a package always produces at least one static library. Which is implied with
staticlibs
.Chocobo1 commented on 2022-12-08 16:17 (UTC) (edited on 2022-12-08 16:24 (UTC) by Chocobo1)
I reckon
devtools
is for building "official repository packages". And AUR packages aren't viewed as official (this impression comes from a bug wrangler).Quoting from README.md:
I would rather not bother with it unless truly necessary. If people want to build with LTO then they should setup their default build flags properly. Also IMO injecting the build flag package-by-package doesn't scale well and doesn't feel right.
While we are at it, why don't they add
-ffat-lto-objects
to devtools build flags?abouvier commented on 2022-12-08 15:35 (UTC)
It's enabled in
devtools
: https://gitlab.archlinux.org/archlinux/devtools/-/blob/master/config/makepkg/x86_64.conf#L97On the other hand
staticlibs
is disabled in bothpacman
anddevtools
by default :pyochananmarqos commented on 2022-12-08 15:35 (UTC)
@Chocobo1: Yes, I'm aware it's not enabled by default with
pacman
. However, it is withdevtools
. Perhaps just disable it then?Chocobo1 commented on 2022-12-08 15:22 (UTC) (edited on 2022-12-08 15:24 (UTC) by Chocobo1)
No. LTO is not enabled by default: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.0.2/etc/makepkg.conf.in#L93
Use that flag for your own builds instead.
yochananmarqos commented on 2022-12-08 15:00 (UTC)
@Chocobo1: Please add
export CFLAGS+=" -ffat-lto-objects"
to the build() function to avoid mangling when stripping with LTO enabled. See Task Todo List LTO fat objects.Chocobo1 commented on 2022-11-14 05:53 (UTC)
Done.
1 2 Next › Last »