Emerge of gstreamer-0.8.11 terminates with the following compilation error: ../../gst/.libs/libgstreamer-0.8.so: undefined reference to `vgPlain_tool_info' valgrind-3.1.0 is installed on the system, too. If I: a) unmerge valgrind before emerging gstreamer, or b) add "--disable-valgrind" to gstreamer's configure options, compilation succeeds. Reproducible: Always Steps to Reproduce: 1. emerge gstreamer Actual Results: [...] i686-pc-linux-gnu-gcc -march=pentium-m -O2 -pipe -o .libs/spidertest spidertest-spidertest.o ../../gst/.libs/libgstreamer-0.8.so -L/usr/lib/valgrind/x86-linux /usr/lib/libxml2.so -lz /usr/lib/libgobject-2.0.so /usr/lib/libgthread-2.0.so -lpthread /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so /usr/lib/libpopt.so -lcoregrind -lvex -lgcc -lm ../../gst/.libs/libgstreamer-0.8.so: undefined reference to `vgPlain_tool_info' collect2: ld returned 1 exit status make[4]: *** [spidertest] Error 1 # emerge info Portage 2.0.53 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14-gentoo-r4 i686) ================================================================= System uname: 2.6.14-gentoo-r4 i686 Intel(R) Pentium(R) M processor 1.73GHz Gentoo Base System version 1.12.0_pre11 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/fax /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control /var/spool/fax/etc" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium-m -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://a1igentoo.kph.uni-mainz.de/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://gentoo.oregonstate.edu http://gentoo.inode.at" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X Xaw3d aalib acpi alsa audiofile avi berkdb bitmap-fonts bzip2 cdparanoia cdr clisp crypt curl dvd dvdr eds emacs emacs-w3 emboss encode esd ethereal exif expat fam fbcon foomaticdb fortran gcj gdbm gif glut gnome gpm gstreamer gtk gtk2 idea idn ieee1394 imagemagick imap imlib ipv6 java jpeg lcms libcaca libg++ libwww lua mad mikmod mmx mng motif mozilla mp3 mpeg ncurses nls nocd nptl nptlonly nsplugin offensive ogg oggvorbis opengl oss pcmcia pcre pdflib perl png postgres python qt quicktime readline recode sdl skey slang sox spell sse sse2 ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts udev usb vorbis wifi win32codecs wxwindows xine xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
same problem here with valgrind-3.1.0
*** Bug 115502 has been marked as a duplicate of this bug. ***
Confirming. Same problem here on a "stable" x86 machine running valgrind-3.1.0 (selective ~x86) and gstreamer-0.8.11 (selective ~x86). Regards, Florian
I've just reproduced like problem on ~amd64
Same issue here - however, unmasking 0.10.0 and emerging it worked fine... Just in case people aren't wanting to do that, I'm going to post a modified 0.8.11 ebuild in a moment that has a valgrind USE flag that you can disable in order to do a --disable-valgrind on the gstreamer configure.
Created attachment 75285 [details] Modified ebuild to have valgrind USE flag - disabled does a --disable-valgrind on econf
(In reply to comment #5) > Just in case people aren't wanting to do that, I'm going to post a modified > 0.8.11 ebuild in a moment that has a valgrind USE flag that you can disable in > order to do a --disable-valgrind on the gstreamer configure. Sorry, but this doesn't look like a reasonable solution: What could be the purpose of a USE flag that only leads to broken behaviour if it is enabled? Besides, there are more than enough USE flags already.
In the ChangeLog of gstreamer-0.10.0 there is the following comment: 2005-11-16 Michael Smith <msmith@fluendo.com> * gst/Makefile.am: Don't link against VALGRIND_LIBS. That was always the wrong thing to do, but only breaks with newer valgrind versions. We're not a valgrind tool, we have no link-time dependencies on libcoregrind. Excluding VALGRIND_LIBS from GST_LIB_LIBS fixes the issue for version 0.8.11, too. See attached patch.
Created attachment 75318 [details, diff] gstreamer-0.8.11-valgrind_libs.patch
could someone please put this patch in the ebuild ?
May I point out that this version of gstreamer has now been marked stable? On amd64 this means that when valgrind becomes stable (which it can when no bugs are open on valgrind - this bug does not seem a valgrind bug), re-emerging gstreamer will fail miserably. I don't have a stable x86, I just hope that the latest valgrind stable combined with gstream-0.8.11 doesn't trigger the issue.
(In reply to comment #11) > May I point out that this version of gstreamer has now been marked stable? > I don't have a stable x86, I just hope that the latest valgrind stable combined > with gstream-0.8.11 doesn't trigger the issue. Latest stable valgrind on x86 is 2.4.0 which is one year old. It does not trigger the issue. Added the Gnome Desktop team to the cc list since the Gstreamer herd seems to be silent.
added --disable-valgrind to econf in cvs.
