New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmake find_package fails due to too restrictive permissions of /usr/local/lib64/cmake directory #1634
Comments
Important note: I ran the installation inside a docker container where umask was 0027 which is a more restrictive mask then the host's 0022. And I think this is the main cause. |
Sounds plausible. If you install things with insufficient permission to allow others to read them, then it won't be much surprise when they fail because they can't read them. |
It isn't clear to me that there is anything really for me to do here. The relevant rules are:
I suppose I could add the FILE_PERMISSIONS and DIRECTORY_PERMISSIONS attributes to those command lines instead of relying on the default, but I'm not sure that's a great idea. I honestly think if you use a very strict umask (like 027), then you probably want that umask to be honored. If that means that stuff breaks for stuff you installed for others (for example while operating in a root account) -- perhaps the umask setting is contra-indicated? Put another way, I don't feel comfortable changing (or overriding) a umask that a user may have set here. |
I'm closing this as "won't fix" for now. |
Describe the bug
Trying to build my code with nng. When I put this line to my CMakeLists.txt:
then cmake fails, it cannot find the necessary cmake files:
Expected behavior
find_package should run successfully.
Actual Behavior
find_package fails.
To Reproduce
Create a CMakeLists.txt which calls find_package for nng
** Environment Details **
nng build with master 5385b78
Additional context
I found that nng cmake files are installed, but the cmake directory is not accessible.
I had to do chmod 755 to the directory and then it was OK.
The text was updated successfully, but these errors were encountered: