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 1313260 - liblas-config reports wrong libraries
Summary: liblas-config reports wrong libraries
Keywords:
Status: CLOSED DUPLICATE of bug 1300860
Alias: None
Product: Fedora
Classification: Fedora
Component: liblas
Version: 23
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Devrim Gündüz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 09:30 UTC by Thomas Kreuzer
Modified: 2016-03-04 08:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-04 08:22:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
liblas.spec bug fix (4.54 KB, text/plain)
2016-03-04 08:33 UTC, Thomas Kreuzer
no flags Details

Description Thomas Kreuzer 2016-03-01 09:30:59 UTC
Description of problem:

liblas-config refers to the following libraries

  libboost_program_options.so
  libboost_thread.so
  libgeotiff.so
  liblaszip.so

however, those library names are not present on Fedora 23, they are:

  libboost_program_options.so.1.58.0
  libboost_thread.so.1.58.0
  libgeotiff.so.2
  liblaszip.so.6

I am not sure whether liblas-config should be patched or the corresponding libraries should create the appropriate symlinks.
There certainly are a few easy ways to patch liblas-config, but I am not sure what is considered best practice.

Version-Release number of selected component (if applicable):
liblas-1.8.0-7

Comment 1 Thomas Kreuzer 2016-03-04 08:22:57 UTC

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

Comment 2 Thomas Kreuzer 2016-03-04 08:33:33 UTC
Created attachment 1133109 [details]
liblas.spec bug fix


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