Package Details: libbacktrace-git r87.g11427f3-1

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-3-Clause
Conflicts: libbacktrace
Provides: libbacktrace, libbacktrace.so
Submitter: Chocobo1
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 14
Popularity: 0.89
First Submitted: 2019-04-16 04:00 (UTC)
Last Updated: 2024-06-05 02:55 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

yochananmarqos commented on 2022-12-08 15:35 (UTC)

@Chocobo1: Yes, I'm aware it's not enabled by default with pacman. However, it is with devtools. Perhaps just disable it then?

options=('!lto')

Chocobo1 commented on 2022-12-08 15:22 (UTC) (edited on 2022-12-08 15:24 (UTC) by Chocobo1)

Please add export CFLAGS+=" -ffat-lto-objects" to the build() function to avoid mangling when stripping with LTO enabled.

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.

  -> Stripping unneeded symbols from binaries and libraries...
strip: ./usr/lib/st3wKOY2/atomic.o: plugin needed to handle lto object
strip: ./usr/lib/stwfszpi/atomic.o: plugin needed to handle lto object

Chocobo1 commented on 2022-11-14 05:53 (UTC)

Could you add pkg-config .pc file?

Done.

DanShaders commented on 2022-04-13 11:43 (UTC)

Could you add pkg-config .pc file?

abouvier commented on 2021-06-15 10:55 (UTC)

Yes it will be useless in this case, but it will not hurt either to add it. And one day, maybe, when versioning will be implemented, the PKGBUILD will already be ready!

Chocobo1 commented on 2021-06-15 07:18 (UTC) (edited on 2021-06-15 07:19 (UTC) by Chocobo1)

This will allow pacman, before an update, to detect when a package dependent on libbacktrace needs a rebuild (because of a soname bump). Instead of updating and making the package unusable.

OK, I understand this part. The next question is, does it make sense to apply this practice to a library that doesn't maintain soname versioning? If you really build this package you'll notice that libbacktrace always uses 0.0.0, I take that the author doesn't care about it and the users are required to always rebuilt the client app/lib upon upgrading.

abouvier commented on 2021-06-15 06:09 (UTC)

This will allow pacman, before an update, to detect when a package dependent on libbacktrace needs a rebuild (because of a soname bump). Instead of updating and making the package unusable.

https://bugs.archlinux.org/task/58947

Chocobo1 commented on 2021-06-15 03:49 (UTC)

Can you add libbacktrace.so to the provides array, as recommended in the Arch package guidelines.

I'm curious, when do you need it where depends=('libbacktrace') won't satisfy?

abouvier commented on 2021-06-14 21:53 (UTC) (edited on 2021-06-14 21:55 (UTC) by abouvier)

Can you add libbacktrace.so to the provides array, as recommended in the Arch package guidelines.

« First ‹ Previous 1 2 3 Next › Last »