Package Details: auracle-git r366.8739929-5

Git Clone URL: (read-only, click to copy)
Package Base: auracle-git
Description: A flexible client for the AUR
Upstream URL:
Keywords: aur
Licenses: MIT
Conflicts: auracle
Provides: auracle
Submitter: Foxboron
Maintainer: artafinde
Last Packager: artafinde
Votes: 122
Popularity: 1.83
First Submitted: 2017-07-02 16:40 (UTC)
Last Updated: 2022-07-04 23:33 (UTC)

Pinned Comments

artafinde commented on 2022-01-26 09:15 (UTC) (edited on 2022-01-29 10:24 (UTC) by artafinde)

If the build fails:

  • Clear your aur helper cache and SRCPKGDEST directory
  • Rebuild in clean chroot 1
  • If it still fails, use a paste bin 2 to show full build logs

There's a package build already which you can try out from my repo.

falconindy commented on 2020-05-31 15:35 (UTC)


  • The dependencies are correct. fmt and nlohmann_json are configured as subprojects for ease of development on my end, and it's only natural to statically link C++ projects, as ABI stability with exported C++ libraries isn't a thing (compared to C).
  • If you think pod2man is missing, it's a configuration problem on your end. pod2man is part of the perl package, but in a perl-specific PATH handled by /etc/profile.d/
  • I'm only able to test auracle on i686 and x86_64, so that's what I'm willing to commit to in the PKGBUILD. If you want to build this on some other architecture, use makepkg -A. The "any" architecture is reserved for packages with architecture independent files (and compiled C++ is not).

Latest Comments

1 2 3 4 5 6 .. 24 Next › Last »

artafinde commented on 2022-11-06 13:38 (UTC)

slondr: Unfortunately not all aarch64 CPU support the same set of instructions and abseil dependency uses some of those. The fact it's built successful in one aarch64 doesn't mean it will on some other.

slondr commented on 2022-11-06 02:44 (UTC)

Compiled perfectly fine without modification of any sort on my aarch64 pinephone, just using makepkg -A. Is there any appetite for an update to the PKGBUILD? If not, I can throw up an auracle-aarch64 package or something like that.

Cody_Learner commented on 2022-09-08 15:35 (UTC) (edited on 2022-12-08 14:44 (UTC) by Cody_Learner)

This package will not be buildable on older AMD processors due to enabling newer CPU features in menson, or is it something else?

Sounds like installing the newer pre-built version to use with my old processor would possibly be problematic as well?

If this is the case, perhaps someone could offer a fork for old CPU version with the appropriate mods. If I knew more, I'd do it...

Model name: AMD Phenom(tm) 9850 Quad-Core Processor

lscpu | awk '/Flags/ {$1=" "; print $0}' | xargs -n1 | sort | grep -Ei 'CMP|XCHG|L-|AHF|POP|SSE|SSS'








EDIT: I settled on downloading/installing into/from my local AUR repo, a prebuilt current version binary from chaotic-aur.

Warning! Chaotic AUR is a third-party repository

artafinde commented on 2022-07-29 19:42 (UTC)

@PS0: that's a limitation of meson. There is an open issue on meson about this and probably won't be fixed. :(

PS0 commented on 2022-07-29 19:06 (UTC)

@artafinde It works for Auracle, but if someone would use the random library on an old CPU, it probably will fail as too many files are compiled with -sse4.1.

artafinde commented on 2022-07-29 15:32 (UTC)

@PS0 If possible try replacing the PKGBUILD with this and let me know if it works. If yes I Will try to push it upstream.

artafinde commented on 2022-07-29 13:05 (UTC) (edited on 2022-07-29 13:08 (UTC) by artafinde)

@PS0 I see that is meson-wrap specific then - raised

PS0 commented on 2022-07-29 12:41 (UTC)

@artafinde abseil-cpp uses -maes and -msse4.1 only on and The meson wrap enables these flags globally, which is not what the abseil-cpp developers intended.

artafinde commented on 2022-07-29 11:15 (UTC)

@PS0, do you see the flags being used when you compile abseil-cpp with cmake? If yes then raise an issue with abseil-cpp on github. If not then it might be coming from the meson wrap. My AMD CPU has SSE4.1 extension so can't reproduce it.

gatsby commented on 2022-07-29 10:37 (UTC)

@PS0 Thanks, in my case I only had these sse flags available: sse sse2 ssse3 sse4a.