localhost portage # emerge =audacious-plugins-1.2.2-r1 audacious Calculating dependencies... done! >>> Emerging (1 of 2) media-plugins/audacious-plugins-1.2.2-r1 to / ..<<Some stuff>>.. AudioCompressor (AGC): yes LADSPA effects host (ladspa): yes Voice Removal: yes Visualization ------------- Blur Scope: yes Paranormal Visualization Library: yes Container --------- Winamp PLS playlist format (pls): yes M3U playlist format (m3u): yes XML Sharable Playlist Format (xspf): yes CC cdaudio.c CC cdinfo.c CC cddb.c CC configure.c CC http.c cdaudio.c: In function ‘cdda_get_tuple’: cdaudio.c:1069: error: ‘TitleInput’ has no member named ‘length’ cdaudio.c: In function ‘get_song_info’: cdaudio.c:1257: error: ‘TitleInput’ has no member named ‘length’ make[3]: *** [cdaudio.o] Error 1 make[2]: *** [build] Error 2 make[1]: *** [build] Error 2 make: *** [build] Error 2 !!! ERROR: media-plugins/audacious-plugins-1.2.2-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile audacious-plugins-1.2.2-r1.ebuild, line 90: Called die !!! make failed !!! If you need support, post the topmost build error, and the call stack if relevant. Reproducible: Always
Created attachment 106249 [details] full output of emerge
*** This bug has been marked as a duplicate of bug 148280 *** *** This bug has been marked as a duplicate of bug 148280 ***
Created attachment 106251 [details] emerge info
Created attachment 106344 [details] audacious build log
This is not a dupe of the bug specified. Itried to find an odd build of audacious but in vain. There is something else wrong:( (In reply to comment #5) > I'm missing configure.log output, which will tell me why the CDDA includes are missing. Main question: Where is configure.log? > Does 1.2.0 (non-r1) build correctly? > I have a sneaking suspicion that you built Audacious from SVN or otherwise > outside of portage once, and that it is living in /usr/local. Would you mind > checking that, and deleting it if necessary? No. There is no odd build. > Also, make sure that you do not > use --nodeps or anything along those lines. No. Flags are ok. > Last but not least, you can log the output using: > emerge audacious &> audacious.buildlog I've read this bug report before - this is not my case. I didn't use SVN version of audacious.
(In reply to comment #5) > This is not a dupe of the bug specified. It is not an exact duplicate, but it is related. Your problem is a set of stray includes. Use the following command to find them: locate beepctrl.h You may have to emerge slocate if this wasn't on your system already. In that case, run updatedb, then try the locate command. > Itried to find an odd build of audacious but in vain. The command above will help you. > Main question: > Where is configure.log? It'll be in the working directory, which you can find under: /var/tmp/portage/media-plugins/audacious-plugins-1.2.2-r1/work/
(In reply to comment #5) > This is not a dupe of the bug specified. Actually, it is. At any rate, you have a stale SDK installed somewhere. Comment #6 has info on how to find it.
Created attachment 106458 [details] config.log
# locate beepctrl.h /usr/include/audacious/beepctrl.h /usr/include/audacious/audacious/beepctrl.h
(In reply to comment #9) > # locate beepctrl.h > /usr/include/audacious/beepctrl.h > /usr/include/audacious/audacious/beepctrl.h > `rm -rf /usr/include/audacious/audacious` will fix it.
Stale includes identified. This is not a problem in audacious or in the ebuild. The solution given in comment #10 is correct.
