Bug 551277 - valgrind-devel package is inconsistent
Summary: valgrind-devel package is inconsistent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-29 18:54 UTC by Sven Herzberg
Modified: 2010-01-29 03:23 UTC (History)
2 users (show)

Fixed In Version: 3.5.0-14.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-20 10:47:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sven Herzberg 2009-12-29 18:54:16 UTC
Description of problem:
The pkg-config file refers to a library that's not there.

Version-Release number of selected component (if applicable):
$ rpm -q valgrind-devel
valgrind-devel-3.5.0-9.i686

How reproducible:
# echo "void main (void) {}" | gcc -x c `pkg-config --cflags --libs valgrind`

Steps to Reproduce (in bash):
1. "export LC_ALL=C"
2. execute the command above
  
Actual results:
3. There is no "a.out" file; instead there is this error message:
> /usr/bin/ld: cannot find -lcoregrind
> collect2: ld returned 1 exit status

Expected results:
3. There is an "a.out" file.

Comment 1 Sven Herzberg 2009-12-30 18:40:12 UTC
There seems to be a similarly-called library, maybe a symlink is enough:

$ rpm -ql valgrind{,-devel} | grep coreg
/usr/lib/valgrind/libcoregrind-x86-linux.a

Comment 2 Jakub Jelinek 2010-01-20 10:47:44 UTC
Should be fixed in http://koji.fedoraproject.org/packages/valgrind/3.5.0/14.fc12/

Comment 3 Fedora Update System 2010-01-22 08:57:23 UTC
valgrind-3.5.0-14.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/valgrind-3.5.0-14.fc12

Comment 4 Fedora Update System 2010-01-29 03:22:54 UTC
valgrind-3.5.0-14.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.