Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 291144 - media-plugins/gst-plugins-vorbis-0.10.23 fails to emerge
Summary: media-plugins/gst-plugins-vorbis-0.10.23 fails to emerge
Status: RESOLVED DUPLICATE of bug 283761
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-30 11:59 UTC by Alan Hourihane
Modified: 2009-10-30 12:07 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Hourihane 2009-10-30 11:59:12 UTC
* Building external plugin ...
make -j4 
  CC    vorbis.o
  CC    vorbisdec.o
  CC    vorbisenc.o
  CC    vorbisparse.o
  CC    vorbistag.o
  LINK  libgstvorbis.la
/bin/grep: /usr/lib64/libogg.la: No such file or directory
/bin/sed: can't read /usr/lib64/libogg.la: No such file or directory
libtool: link: `/usr/lib64/libogg.la' is not a valid libtool archive
make: *** [libgstvorbis.la] Error 1
 * 
 * ERROR: media-plugins/gst-plugins-vorbis-0.10.23 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2370:  Called gst-plugins-base_src_compile
 *             environment, line 1737:  Called die
 * The specific snippet of code:
 *       emake || die "compile failure"
 *  The die message:
 *   compile failure
 * 
 * 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/gst-plugins-vorbis-0.10.23/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-plugins/gst-plugins-vorbis-0.10.23/temp/environment'.
 *
Comment 1 Sebastian Luther (few) 2009-10-30 12:07:34 UTC
"emerge --sync" and "emerge -1 gcc" should fix it.

*** This bug has been marked as a duplicate of bug 283761 ***