Package Details: ashuffle 3.11.1-1

Git Clone URL: (read-only, click to copy)
Package Base: ashuffle
Description: Automatic library-wide shuffle for mpd.
Upstream URL:
Licenses: MIT
Submitter: oi_wtf
Maintainer: oi_wtf
Last Packager: oi_wtf
Votes: 4
Popularity: 0.68
First Submitted: 2019-09-20 18:25
Last Updated: 2021-03-15 08:38

Dependencies (5)

Required by (0)

Sources (1)

Latest Comments

oi_wtf commented on 2020-06-10 06:55

This is probably the reason:

/usr/bin/ld: /usr/lib/gcc/armv7l-unknown-linux-gnueabihf/9.3.0/../../../libabsl_str_format_internal.a: error adding symbols: file format not recognized

Please look at the output of

objdump -a /usr/lib/libabsl_str_format_internal.a

Specifically the "file format" of the object files.

I was planning to update this package to 3.5 as soon as gtest 1.10 hit [community], it was in [community-testing] for a while. Since this happened now, I'll update soon.

Please note, there is a package ashuffle-git that does the building the "git way", which worked for you. Since current master almost always matches the latest release, there's no "harm" in using it.

keithspg commented on 2020-06-09 13:43

If I go to the git archive and build according to the instructions, I get a fully built binary:

git clone
git checkout v3.5.0
git submodule update --init --recursive
meson -Dbuildtype=release build
ninja -C build

I think the PKGBUILD file needs to be adjusted somehow.

keithspg commented on 2020-06-09 13:17

I finally was able to get the pre-requisites set up to build this. I am trying to build for RPi (armv6h and armv7h). I was able to build the 2.0.1, but cannot build 3.4.0. I also tried 3.5.0 (latest release from the git repository) and get the same result. In case anyone is curious, I had to build the abseil-cpp on x86-64 (it is not arch dependent and requires more memory to build than the RPIb3+ has) and build and install the 2 packages generated by g-test. When I try to build this, though, I get this:

Found ninja-1.10.0 at /usr/bin/ninja
ninja: Entering directory `builddir'
[19/49] Linking target rule_test
FAILED: rule_test
c++  -o rule_test 'rule_test@exe/' 'rule_test@exe/' 'rule_test@exe/' 'rule_test@exe/' 'rule_test@exe/' 'rule_test@exe/' 'rule_test@exe/' -Wl,--as-needed -Wl,--no-undefined -pie -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16 -O2 -pipe -fstack-protector-strong -fno-plt -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,--start-group -labsl_raw_logging_internal -labsl_int128 -labsl_str_format_internal -labsl_strings_internal -labsl_strings -labsl_hash -labsl_city -pthread /usr/lib/pkgconfig/../../lib/ -lpthread /usr/lib/pkgconfig/../../lib/ /usr/lib/pkgconfig/../../lib/ -Wl,--end-group
/usr/bin/ld: /usr/lib/gcc/armv7l-unknown-linux-gnueabihf/9.3.0/../../../libabsl_str_format_internal.a: error adding symbols: file format not recognized
collect2: error: ld returned 1 exit status
distcc[8073] ERROR: compile (null) on localhost failed
[24/49] Compiling C++ object 'shuffle_test@exe/'
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in build().

oi_wtf commented on 2020-04-12 21:41

It is possible if I started using VCS sources. But when the release tarball is used, it is not that easy.

Since the current approach is not broken and libtap does not update very often, I wont change the source from the tarball to git for this package. (If you want git, take a look at ashuffle-git )

dos1 commented on 2020-04-11 23:44

libtap could be included via a git submodule instead, see: