Bug 1193328

Summary:	rpmbuild should leave PKG_CONFIG_PATH alone
Product:	Red Hat Enterprise Linux 7	Reporter:	Marek Marusic <mmarusic>
Component:	rpm	Assignee:	Florian Festi <ffesti>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	low
Version:	7.1	CC:	jherrman
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If a Perl script in a package contained a string declared as a here-document that included the "use" or "require" words, or a multiline string with these words, the package in some cases had incorrect dependencies when it was created using the "rpmbuild" command. Now, the "use" and "require" strings are ignored as keywords in here-documents and multiline strings, which prevents the problem from occurring.	Story Points:	---
Clone Of:	921969	Environment:
Last Closed:	2015-03-17 16:24:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marek Marusic 2015-02-17 07:41:30 UTC

Present also on RHEL7

Version-Release number of selected component:
4.11.1-25.el7

+++ This bug was initially created as a clone of Bug #921969 +++

Fix available upstream.


+++ This bug was initially created as a clone of Bug #569773 +++

Description of problem:
If you want to build a package which is depended on another package, and detects it with pkgconfig it won't get detected if this other package is in a non standard path (which was set in PKG_CONFIG_PATH)
The patch from bug 212522 creates this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=212522

Version-Release number of selected component (if applicable):
4.4.2.3-18

How reproducible:

Steps to Reproduce:
1. install/build something with another prefix path (for example /usr/broken), with a pkgconfig file, like eventlog: http://www.balabit.com/downloads/files/eventlog/0.2/
2. set PKG_CONFIG_PATH to the prefix path from step 1
3. build something with rpmbuild which detects in it's configure where the package from step 1 is located, like syslog-ng: http://www.balabit.com/downloads/files/syslog-ng/
  
Actual results:
pkgconfig reports the package is not found, this works when building from commandline, or with all rpm(build) packages before 4.4.2.3-18

Expected results:
pkgconfig should find the package.

Additional info:
The PKG_CONFIG_PATH is actually set by another package we build.

Proposed fix:
Modify the patch form the other the bug mentioned above so it does not overwrite the PKG_CONFIG_PATH but extends it.

Comment 1 Florian Festi 2015-03-17 16:24:23 UTC


*** This bug has been marked as a duplicate of bug 921973 ***