GNOME Bugzilla – Bug 330308
undefined reference to `vgPlain_tool_info'
Last modified: 2006-02-08 14:40:16 UTC
Hi, Since the latest pre-release, 0.8.11.2, I get a build failure which seems related to valgrind when trying to build GStreamer: cc -g -Wall -O2 -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' This is also mentionned in: http://www.mail-archive.com/gnome-desarrollo@es.gnome.org/msg00061.html (no answer) And in: http://mail.gnome.org/archives/garnome-list/2005-December/msg00105.html Perhaps a valgrind version check is missing in configure? Or perhaps GStreamer shouldcheck for a specific function it uses? Cheers,
Both my sourcetree and my whole system don't have that symbol, and never had it. I don't know where it comes from. Any hint? Maybe a bug or API change in newer valgrinds? --disable-valgrind will do the trick for now. Maybe worth putting in the release notes.
Created attachment 58904 [details] [review] patch against gstreamer 0.8.11 configure.ac This happens with valgrind >= 3.1.0. The solution is not to link to the valgrind libraries at all, which isn't necessary anyway (that's what got applied to 0.10).
Ronald, yeah, I --disabled-valgrind when I saw this. Arwed, does that mean there's no valgrind related code anymore if you don't need to link with it? Ie, should valgrind support we disabled anyway because it's not necessary anymore?
No, it's just that the valgrind stuff that is used in client programs is entirely macro based. Linking to the valgrind libs is only needed for valgrind tools, like memcheck and cachegrind.
Fixed in next prerelease, thanks Arwed.