MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014483CMakeCMakepublic2013-10-14 17:022016-06-10 14:31
ReporterRob Stewart 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformLinuxOSSLESOS Version11SP1
Product VersionCMake 2.8.11.2 
Target VersionFixed in Version 
Summary0014483: RPATH_CHANGE can't update binaries installed with 0444 permissions
DescriptionMy INSTALL() command specifies OWNER_READ GROUP_READ and WORLD_READ only. By the time Cmake arranges for the RPATH/RUNPATH to be updated, the file has 0444 permissions. Since it isn't writable, "Error opening file for update" results.

(FYI, I'm using the UNIX Makefiles generator.)

It seems that the RUNPATH should be updated before INSTALL() does its work or else the update code needs to make the file writable, update the RUNPATH, and then restore the original permissions.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-10-14 17:02Rob StewartNew Issue
2013-10-15 09:14Brad KingNote Added: 0034122
2013-10-15 09:14Brad KingStatusnew => backlog
2016-06-10 14:29Kitware RobotNote Added: 0042391
2016-06-10 14:29Kitware RobotStatusbacklog => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0034122)
Brad King   
2013-10-15 09:14   
cmSystemTools::ChangeRPath and cmSystemTools::RemoveRPath can be taught to adjust the permissions before opening the files for update. These code paths are only reachable through the internal/undocumented file(RPATH_*) commands, and they are only invoked by the generated installation code where we know it is okay to modify the files.
(0042391)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.