Bug #1027

Compile crashes on Ubuntu 20.04.1LTS (ARM64/RPi4B)

Added by Frank Argberg about 1 year ago. Updated 10 months ago.

Target version:
Start date:
September 29, 2020
Due date:
% Done:


Estimated time:
Affects version:


Hi there!

First of all -- thanks for all the great work you've done with Audacious, it's by far my favorite player for Linux! :o)

As I was merrily compiling the latest GitHub version today (Sept 29.,2020), I noticed I had a problem while compiling the "audacious-plugins" git repo.

Distro is Ubuntu 20.04.1LTS (64-bit), aarch64/ARM64 on a Raspebrry Pi 4B. All my junk should be up to date.

Ran the normal ./ , ./configure (no flags), make -j4 .

What I got as an error was:

/usr/bin/ld: plugin.plugin.o: in function `GlobalHotkeys::GlobalHotkeys::GlobalHotkeys()':
/home/ubuntu/builds/audacious-plugins/src/qthotkey/ undefined reference to `GlobalHotkeys::GlobalHotkeys::info'
/usr/bin/ld: /home/ubuntu/builds/audacious-plugins/src/qthotkey/ undefined reference to `GlobalHotkeys::GlobalHotkeys::info'
collect2: error: ld returned 1 exit status
Failed to link!
make[5]: *** [../../] Error 1
make[4]: *** [../../ all] Error 2
make[3]: *** [../ qthotkey] Error 2
make[3]: *** Waiting for unfinished jobs....
Successfully compiled (plugin).
Successfully compiled (plugin).
Successfully compiled (plugin).
Successfully linked
Leaving directory streamtuner.
make[2]: *** [../ all] Error 2
make[1]: *** [ src] Error 2
make: *** [ all] Error 2

I tried re-running and figuring out different things (the meson build also failed, so...) and eventually I just thought I'd sudo make install it as a prank. Lo and behold, everything seems to be working just fine!(?) I'm now running the 4.1-devel version according to Audacity. Haven't noticed any stability issues yet, but then again I'm not using most of the plugins either, mostly just the VU's and so forth.

Let me know if you want me to probe deeper into the issue or if you need any further information (i.e. ./configure 's output, etc.)



#1 Updated by Frank Argberg about 1 year ago

Additional notes:

- The version affected is the latest (Sept. 29, 2020 18:00EEST) GitHub repo clone = 4.1-devel, NOT 4.0.4, and specifically the audacious-plugins repo.
- This happened upon compiling audacious-plugins from source. Had no problems compiling audacious itself from the other GitHub repo.
- Was still able to sudo make install afterwards, and as for now: "What, me worry?"


#2 Updated by John Lindgren 12 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed
  • Affects version deleted (4.0.4)

#3 Updated by Thomas Lange 10 months ago

  • Target version set to 4.1

Also available in: Atom PDF