Summary: | gstreamer 0.8.1 does not compile because of valgrind (valgrind_printf and valgrind_malloc_like macros not defined) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | davi <davicastro> |
Component: | [OLD] Library | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | otte |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Patch to fix gstreamer-0.8.1 ebuild by disabling debug |
Description
davi
2004-06-15 04:37:30 UTC
Created attachment 33308 [details, diff]
Patch to fix gstreamer-0.8.1 ebuild by disabling debug
i'll check it when updating.. added a debug USE flag to gstreamer-0.8.2 to give the choice. That should take care of this for now. reverted that change after a little talk with the gstreamer devs who say it's not wise to disable debug by default. This looks like a bug with your valgrind. GStreamer detects the availability of valgrind headers via pkgconfig. And the pkgconfig support for valgrind is younger than those macros, so you can't have a too old valgrind version. fyi, VALGRIND_PRINTF is part of valgrind.h, the other macros are part of memcheck.h It is actually a problem with my valgrind version, but mine is the version from the portage tree. VALGRIND_MALLOCLIKE_BLOCK and VALGRIND_FREELIKE_BLOCK are in the memcheck.h header, but VALGRIND_PRINTF simply doesn't exist: bash-2.05b$ tar xjf /usr/portage/distfiles/valgrind-2.0.0.tar.bz2 bash-2.05b$ cd valgrind-2.0.0/ bash-2.05b$ grep -r VALGRIND_PRINTF * bash-2.05b$ Although it does exist in valgrind-2.1.1.tar.bz2 (unstable version), which is not in portage yet. You are right. 2.0.0 in fact does not include VALGRIND_PRINTF. The GStreamer configure script should probably check for valgrind >= 2.1. I'll fix that upstream tonight. Fixing the ebuild configure is probably up to foser :) umm yeah..got a bit stuffed with other things. I guess this is already fixed now in newer versions.. still need to check though. checked, all good now, thnx |