Package Details: bloaty-git 1.0.r62.g7cf6c58-1

Git Clone URL: (read-only, click to copy)
Package Base: bloaty-git
Description: A size profiler for binaries
Upstream URL:
Keywords: elf profiler size
Licenses: Apache
Conflicts: bloaty
Submitter: Yamakaky
Maintainer: aperez
Last Packager: aperez
Votes: 6
Popularity: 0.013648
First Submitted: 2016-11-11 23:04 (UTC)
Last Updated: 2020-04-14 09:13 (UTC)

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

cschramm commented on 2023-12-18 10:58 (UTC)

Here's a patch to use the system absl:

--- ./CMakeLists.txt
+++ ./CMakeLists.txt
@@ -50,6 +50,8 @@ else(${PKG_CONFIG_FOUND})

 # Set default build type.
   message(STATUS "Setting build type to 'RelWithDebInfo' as none was specified.")
@@ -157,7 +159,6 @@ endif(UNIX)


 # Baseline build flags.
@@ -244,6 +245,13 @@ add_library(libbloaty
+if (absl_FOUND)
+  target_link_libraries(libbloaty PUBLIC absl::base absl::strings absl::numeric)
+  include_directories(third_party/abseil-cpp)
+  target_sources(libbloaty
     # Until Abseil has a proper CMake build system
     third_party/abseil-cpp/absl/base/internal/ # Grrrr...
@@ -266,7 +274,8 @@ add_library(libbloaty
     # One source file, no special build system needed.
-    )
+  )
 set_property(TARGET libbloaty PROPERTY FOLDER "bloaty")


cschramm commented on 2023-09-25 12:51 (UTC)

The issue is actually that bloaty ships its own version of abseil and the system-provided protobuf has to be compatible with that version. A quick solution for bloaty-git to build is to downgrade protobuf to 21.12-2.

colatkinson commented on 2023-07-26 15:43 (UTC) (edited on 2023-07-26 15:44 (UTC) by colatkinson)

Hey if anyone else is running into building the latest HEAD, this appears to be an upstream issue. Bloaty is vendoring in a bunch of abseil headers, which are incompatible with the version of protobuf that Arch is shipping.

I've filed a bug here: That report also includes a patch that just removes these vendored headers from the CMakeLists. Haven't looked at adding it to the PKGBUILD as yet, but that should provide a temporary workaround.

bpierre commented on 2023-05-07 20:36 (UTC)

Temporary fix for building with GCC 13 (until is merged):

 PKGBUILD | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git i/PKGBUILD w/PKGBUILD
index fe38bce..1b91df8 100644
@@ -13,6 +13,9 @@ conflicts=(bloaty)

 pkgver () {
    cd "${pkgname}"
@@ -22,6 +25,11 @@ pkgver () {

+prepare() {
+  cd "${srcdir}/${pkgname}"
+  patch -p1 -i "${srcdir}/7611debaa6459e66b95e03937a2573316e42b69e.patch"
 build() {
     rm -rf "${srcdir}/build"
     mkdir "${srcdir}/build"

sandsmark commented on 2021-11-08 14:43 (UTC)

It tries to download a ton of stuff in its build() function (so it fails to build here in my sandbox).

I assume it's some submodules it tries to download (instead of using normal dependency handling), so might help to do something like this:

aperez commented on 2020-04-14 09:15 (UTC)

@flacs: Thanks to the suggestion, I have updated the PKGBUILD to depend on system packages instead.

flacs commented on 2020-04-11 16:43 (UTC)

bloaty has the ability to detect system-wide installations of re2, capstone, and protobuf-c, so it would probably make sense to add them as dependencies.

aperez commented on 2018-12-06 20:21 (UTC)

@bertptrs: Thanks for the suggestion, I have updated the PKGBUILD accordingly. Also, tweaked pkgver() to take the tags into account.

bertptrs commented on 2018-12-06 17:19 (UTC)

Hi! Upstream has finally created a release this August, and I've created a package for it. Could you please (for correctness) add a conflict to it?

aperez commented on 2017-10-23 19:55 (UTC)

Upstream has switched to CMake and the PKGBUILD needs to be updated. The following patch works fine for me: