Project

General

Profile

Forums » Audacious »

June 29 commits broke audacious-plugins build

Added by Audacious User2 almost 10 years ago

If I try disabling mp3 plugin, aac plugin spits out same errors about tag_update_stream_metadata
Missing export or am I doing something wrong?

mpg123.plugin.o: In function `mpg123_playback_worker':
/opt/audacious-plugins/src/mpg123/mpg123.cc:353: undefined reference to `tag_update_stream_metadata(Tuple&, VFSFile*)'
mpg123.plugin.o: In function `mpg123_probe_for_tuple':
/opt/audacious-plugins/src/mpg123/mpg123.cc:238: undefined reference to `tag_update_stream_metadata(Tuple&, VFSFile*)'


Replies (3)

RE: June 29 commits broke audacious-plugins build - Added by John Lindgren almost 10 years ago

Try doing a full uninstall (make sure /usr/lib/audacious is completely removed), git clean, rebuild, and reinstall. If the build is really broken, you should see an error at build time. Undefined references at run time usually mean that you have some component (plugin, core, or library) out of date relative to the other components.

RE: June 29 commits broke audacious-plugins build - Added by Audacious User2 almost 10 years ago

Yes, I've done that, and the errors I experience are at building of audacious-plugins.

I can build/install/run audacious alone, but obviously, all I get is the good old:
FATAL: No output plugin found.
(Did you forget to install audacious-plugins?)

RE: June 29 commits broke audacious-plugins build - Added by John Lindgren almost 10 years ago

Oh, sorry. I read "aac plugin spits out" as though you were running Audacious. I looked at the Git log a little while ago and it appears that there were some commits made to libaudtag that broke a number of things. They will probably be reverted.

    (1-3/3)