After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 330308 - undefined reference to `vgPlain_tool_info'
undefined reference to `vgPlain_tool_info'
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
Other Linux
: Normal normal
: 0.8.12
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2006-02-07 20:33 UTC by Loïc Minier
Modified: 2006-02-08 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

patch against gstreamer 0.8.11 (542 bytes, patch)
2006-02-08 08:03 UTC, Arwed v. Merkatz
none Details | Review

Description Loïc Minier 2006-02-07 20:33:00 UTC

Since the latest pre-release,, 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/ -L/usr/lib/valgrind/x86-linux /usr/lib/ -lz /usr/lib/ /usr/lib/ -lpthread /usr/lib/ -ldl /usr/lib/ /usr/lib/ -lcoregrind -lvex -lgcc -lm
../../gst/.libs/ undefined reference to `vgPlain_tool_info'

This is also mentionned in:
(no answer)

And in:

Perhaps a valgrind version check is missing in configure?  Or perhaps GStreamer shouldcheck for a specific function it uses?

Comment 1 Ronald Bultje 2006-02-08 07:20:44 UTC
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.
Comment 2 Arwed v. Merkatz 2006-02-08 08:03:31 UTC
Created attachment 58904 [details] [review]
patch against gstreamer 0.8.11

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).
Comment 3 Loïc Minier 2006-02-08 10:48:05 UTC
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?
Comment 4 Jan Schmidt 2006-02-08 11:08:39 UTC
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.
Comment 5 Ronald Bultje 2006-02-08 14:40:16 UTC
Fixed in next prerelease, thanks Arwed.