Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1937822 - geos-config and pkgconfig are both wrong
Summary: geos-config and pkgconfig are both wrong
Keywords:
Status: CLOSED DUPLICATE of bug 1937443
Alias: None
Product: Fedora
Classification: Fedora
Component: geos
Version: rawhide
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Sandro Mani
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-11 15:43 UTC by Jerry James
Modified: 2021-03-12 12:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-12 12:48:51 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jerry James 2021-03-11 15:43:12 UTC 
Description of problem:
On a Rawhide x86_64 machine:
$ geos-config --clibs
-L/usr/lib@LIB_SUFFIX -lgeos_c
$ pkgconf --libs geos
-L/usr/lib -lgeos_c 

Both of them should either specify "-L/usr/lib64" or no -L flag at all.  The effects of this can be seen in the latest python-shapely build log:

+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s'
cannot open shared object from 'geos-config --clibs': '-L/usr/lib@LIB_SUFFIX -lgeos_c'
there were 2 guess(es) for this path:
	/usr/lib@LIB_SUFFIX/libgeos_c.so
	/usr/lib@LIB_SUFFIX/libgeos_c.so.1

Version-Release number of selected component (if applicable):
geos-3.9.0-2.fc34.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install geos on a 64-bit Rawhide machine
2. Run "geos-config --clibs" and "pkgconf --libs geos"

Actual results:
The incorrect results shown above.

Expected results:
Correct library paths or no explicit library paths.

Additional info:
Comment 1 Sandro Mani 2021-03-12 12:48:51 UTC 
I believe you reproduced this with geos-3.9.1-1.fc35, it should be fixed with geos-3.9.1-2.fc35.

*** This bug has been marked as a duplicate of bug 1937443 ***
Note You need to log in before you can comment on or make changes to this bug.