Description of problem: The pkgconfig information in /usr/lib*/pkgconfig/valgrind.pc contains the variable valt_load_address This was replaced in the valgrind sources from the @VALT_LOAD_ADDRESS@ configure value. Nowadays valgrind defines @VALT_LOAD_ADDRESS_PRI@ and @VALT_LOAD_ADDRESS_SEC@. The old variable is not defined anymore and therefore pkg-config --variable=valt_load_address valgrind produces @VALT_LOAD_ADDRESS@ Version-Release number of selected component (if applicable): How reproducible: valgrind-3.7.0-4.fc17.x86_64 Steps to Reproduce: 1.Install valgrind-devel 2.Run 'pkg-config --variable=valt_load_address valgrind' 3. Actual results: @VALT_LOAD_ADDRESS@ Expected results: Some address Additional info: There are two ways to fix this. Either use VALT_LOAD_ADDRESS_PRI as the value for valt_load_address or introduce two values valt_load_address_pri and vlt_load_address_sec. The same problem is present in Fedora 16.
valgrind-3.8.1-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/valgrind-3.8.1-3.fc18
Package valgrind-3.8.1-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing valgrind-3.8.1-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16133/valgrind-3.8.1-3.fc18 then log in and leave karma (feedback).
valgrind-3.8.1-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/valgrind-3.8.1-3.fc17
valgrind-3.8.1-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.