Bug 509857

Summary: incorrect definition of VTK_LIBRARY_DIRS
Product: [Fedora] Fedora Reporter: Christophe Trophime <christophe.trophime>
Component: vtkAssignee: Axel Thimm <Axel.Thimm>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: orion
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: 5.4.2-33.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-10 21:43:38 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 Christophe Trophime 2009-07-06 15:04:04 UTC
Description of problem:
incorrect definition of VTK_LIBRARY_DIRS in /usr/lib/vtk-5.2/VTKConfig.cmake

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

How reproducible:
always
try to build octaviz for instance
you will see that it is looking for /usrlib/vtk-5.2 directory

Steps to Reproduce:
1.try to build octaviz for instance
2.missing /usrlib/vtk-5.2 directory
3.
  
Actual results:
SET(VTK_LIBRARY_DIRS "${VTK_INSTALL_PREFIX}lib/vtk-5.2")

Expected results:
SET(VTK_LIBRARY_DIRS "${VTK_INSTALL_PREFIX}/lib/vtk-5.2")

Additional info:

Comment 1 Christophe Trophime 2009-07-06 15:26:59 UTC
Same problem with ${VTK_INSTALL_PREFIX}include
Allmost all cmake files are affected in /usr/lib/vtk-5.2

replacing ${VTK_INSTALL_PREFIX} by ${VTK_INSTALL_PREFIX}/ solve the problem

Comment 2 Fedora Update System 2009-07-23 10:24:42 UTC
vtk-5.4.2-33.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/vtk-5.4.2-33.fc11

Comment 3 Fedora Update System 2009-07-23 10:25:05 UTC
vtk-5.4.2-33.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/vtk-5.4.2-33.fc10

Comment 4 Fedora Update System 2009-07-23 19:03:33 UTC
vtk-5.4.2-33.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update vtk'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-7940

Comment 5 Fedora Update System 2009-07-23 19:10:06 UTC
vtk-5.4.2-33.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update vtk'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7958

Comment 6 Fedora Update System 2009-08-01 23:53:06 UTC
vtk-5.4.2-33.fc10, vtkdata-5.4.2-13.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update vtk vtkdata'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-7940

Comment 7 Fedora Update System 2009-08-02 00:02:54 UTC
vtk-5.4.2-33.fc11, vtkdata-5.4.2-13.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update vtk vtkdata'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7958

Comment 8 Fedora Update System 2009-08-10 21:43:15 UTC
vtk-5.4.2-33.fc10, vtkdata-5.4.2-13.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2009-08-10 21:44:22 UTC
vtk-5.4.2-33.fc11, vtkdata-5.4.2-13.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.