Bug 1937443

Summary:	Wrong output from pkgconf geos --libs etc.
Product:	[Fedora] Fedora	Reporter:	Ben Beasley <code>
Component:	geos	Assignee:	Sandro Mani <manisandro>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	devrim, jmlich83, loganjerry, manisandro, tom
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	geos-3.9.1-2.fc35 geos-3.9.1-2.eln110	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-10 18:13:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Beasley 2021-03-10 16:45:09 UTC

Description of problem:

When geos was patched to add the appropriate LIB_SUFFIX (e.g. “64”) as needed, the file geos.pc.cmake should have been patched too.

Version-Release number of selected component (if applicable): 3.9.0-1


How reproducible:


Steps to Reproduce:
1. pkgconf --libs geos

Actual results: (x86_64)

-L/usr/lib -lgeos_c

Expected results: (x86_64)

-L/usr/lib64 -lgeos_c

Additional info:

See also https://bugzilla.redhat.com/show_bug.cgi?id=1937424.

I plan to add another commit to https://src.fedoraproject.org/rpms/geos/pull-request/3 to fix this, too.

Comment 1 Ben Beasley 2021-03-10 17:02:56 UTC

The expected output should actually just be:

-lgeos_c

since pkgconf drops the “usual” libdir.

Fix now available in https://src.fedoraproject.org/rpms/geos/pull-request/3.

Comment 2 Fedora Update System 2021-03-10 18:13:34 UTC

FEDORA-2021-453846ff57 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2021-03-10 18:28:28 UTC

FEDORA-2021-a21afc05c7 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Sandro Mani 2021-03-12 12:48:50 UTC

*** Bug 1937822 has been marked as a duplicate of this bug. ***