Red Hat Bugzilla – Bug 594072
"pkg-config --libs OpenIPMIpthread" fails
Last modified: 2013-10-31 21:33:41 EDT
+++ This bug was initially created as a clone of Bug #591646 +++
Description of problem:
copied from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=474087
# pkg-config --libs OpenIPMIpthread
Package pthread was not found in the pkg-config search path.
Perhaps you should add the directory containing `pthread.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pthread', required by 'OpenIPMIpthread', not found
Please remove bogus pthread from Requires:
and add -pthread to Cflags:
Version-Release number of selected component (if applicable):
both F-9 and F-10 have the issue:
Steps to Reproduce:
1. try to build collectd-4.4.4 with --enable-ipmi
2. see http://koji.fedoraproject.org/koji/getfile?taskID=895839&name=build.log
libopenipmi . . . . no (/usr/bin/pkg-config doesn't know OpenIPMIpthread)
--- Additional comment from email@example.com on 2008-10-22 22:04:03 EDT ---
Thank you for the bug report. At the moment, the Fedora developers are
busy fixing other issues and may not have time to work on this one. The
best way to make sure your problem will get looked on is to report it to
the authors of the program. Most upstream authors use a bug tracking system
like bugzilla, and more people who know the code will be looking at the
bug report there.
The upstream bug tracking system to use is:
You are requested to add the bugzilla link here for tracking purposes.
Please make sure the bug isn't already in the upstream bug tracker
before filing it.
--- Additional comment from firstname.lastname@example.org on 2008-10-23 04:28:55 EDT ---
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.