Leaving directory demac.
Entering directory cdaudio-ng.
Successfully generated dependencies.
Successfully compiled configure.c.
Successfully compiled cdaudio-ng.c.
Successfully linked cdaudio-ng.so.
Leaving directory cdaudio-ng.
Entering directory null.
Successfully generated dependencies.
Successfully compiled null.c.
Successfully linked null.so.
Leaving directory null.
Entering directory alsa.
In file included from audio.c:34:
alsa.h:37:29: error: alsa/pcm_plugin.h: No such file or directory
In file included from configure.c:19:
alsa.h:37:29: error: alsa/pcm_plugin.h: No such file or directory
In file included from alsa.c:19:
alsa.h:37:29: error: alsa/pcm_plugin.h: No such file or directory
make[6]: *** [audio.dep] Error 1
make[6]: *** Waiting for unfinished jobs....
make[6]: *** [configure.dep] Error 1
In file included from about.c:19:
alsa.h:37:29: error: alsa/pcm_plugin.h: No such file or directory
In file included from init.c:21:
alsa.h:37:29:make[6]: *** [alsa.dep] Error 1
error: alsa/pcm_plugin.h: No such file or directory
make[6]: *** [about.dep] Error 1
make[6]: *** [init.dep] Error 1
Failed to generate dependencies!
make[5]: *** [depend] Error 1
make[4]: *** [all] Error 1
make[3]: *** [subdirs] Error 1
make[2]: *** [all] Error 1
make[1]: *** [subdirs] Error 1
make: *** [all] Error 1
*
* ERROR: media-plugins/audacious-plugins-1.5.0 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2394: Called die
* The specific snippet of code:
* emake || die "make failed"
* The die message:
* make failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/media-plugins/audacious-plugins-1.5.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/media-plugins/audacious-plugins-1.5.0/temp/environment'.
*
* Messages for package app-editors/nano-2.1.1:
* More helpful info about nano, visit the GDP page:
* http://www.gentoo.org/doc/en/nano-basics-guide.xml
* Messages for package net-misc/neon-0.26.4:
* There are new features in this version; please beware that
* upstream considers the socks support experimental. If you
* experience test failures (eg, bug 135863) then try rebuilding
* glibc.
*
* Neon has a policy of breaking API across versions, this means
* that any packages that links against neon will be broken after
* updating. They will remain broken until they are ported to the
* new API. You can downgrade neon to the previous version by doing:
*
* emerge --oneshot '<net-misc/neon-0.26'
*
* You may also have to downgrade any packages that have already been
* ported to the new API.
* Messages for package net-print/cups-1.3.6-r3:
* For information about installing a printer and general cups setup
* take a look at: http://www.gentoo.org/doc/en/printing-howto.xml
* Messages for package net-analyzer/wireshark-1.0.0:
* With version 0.99.7, all function calls that require elevated privileges
* have been moved out of the GUI to dumpcap. WIRESHARK CONTAINS OVER ONE
* POINT FIVE MILLION LINES OF SOURCE CODE. DO NOT RUN THEM AS ROOT.
*
* NOTE: To run wireshark as normal user you have to add yourself into
* wireshark group. This security measure ensures that only trusted
* users allowed to sniff your traffic.
* Messages for package net-im/pidgin-2.4.1:
*
* If you experience problems with pidgin, file them as bugs with
* Gentoo's bugzilla, http://bugs.gentoo.org
*
* Be sure to USE="debug" and include a backtrace for any seg
* faults, see http://developer.pidgin.im/wiki/GetABacktrace for details on
* backtraces.
*
* Please read the pidgin FAQ at http://developer.pidgin.im/wiki/FAQ
*
*
* If you experience problems with pidgin, file them as bugs with
* Gentoo's bugzilla, http://bugs.gentoo.org
*
* Be sure to USE="debug" and include a backtrace for any seg
* faults, see http://developer.pidgin.im/wiki/GetABacktrace for details on
* backtraces.
*
* Please read the pidgin FAQ at http://developer.pidgin.im/wiki/FAQ
*
* Messages for package net-misc/openssh-4.9_p1-r1:
* Remember to merge your config files in /etc/ssh/ and then
* restart sshd: '/etc/init.d/sshd restart'.
* Please be aware users need a valid shell in /etc/passwd
* in order to be allowed to login.
* Messages for package gnome-extra/gnome-screensaver-2.20.0-r3:
* If you have xscreensaver installed, you probably want to disable it.
* To prevent a duplicate Screensaver entry in the menu, you need to
* build xscreensaver with -gnome in the USE flags.
* echo "x11-misc/xscreensaver -gnome" >> /etc/portage/package.use
* Information for converting screensavers is located in
* /usr/share/doc/gnome-screensaver-2.20.0-r3/xss-conversion.txt.
* Messages for package media-plugins/audacious-plugins-1.5.0:
*
* ERROR: media-plugins/audacious-plugins-1.5.0 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 2394: Called die
* The specific snippet of code:
* emake || die "make failed"
* The die message:
* make failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/media-plugins/audacious-plugins-1.5.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/media-plugins/audacious-plugins-1.5.0/temp/environment'.
*