Skip to content

make install fails to install core libraries with correct permissions #5742

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

Closed
mstewartgallus opened this issue Apr 5, 2013 · 3 comments
Closed

Comments

@mstewartgallus
Copy link
Contributor

I built Rust from source, and installed it on a Free Software distro (Trisquel 6.0) based off of Ubuntu 12.04. When I installed it I ran into errors compiling a simple hello world test program. The compiler said it could not find the core library. Upon investigation, I found that the installer had not properly set the permissions of the core library folders. I needed to manually set the permissions away from only allowing root to access the libraries to allowing everyone to access the libraries. In code:

chmod g+rx,o+rx /usr/local/lib/rustc/x86_64-unknown-linux-gnu
chmod g+rx,o+rx /usr/local/lib/rustc/x86_64-unknown-linux-gnu/lib

The commands to build were:

./configure
make
sudo make install

Edit: Later today I tried reinstalling with git master (last time I had used the 0.6 release version), and realized that I had accidentally omitted one of the libraries with the incorrect permissions. I had also had to have done:

chmod g+rx,o+rx /usr/local/lib/rustc
@pnkfelix
Copy link
Member

pnkfelix commented Apr 5, 2013

I could not replicate on Mac OS X. I recommend someone try on a Linux machine.

@mstewartgallus
Copy link
Contributor Author

I feel kind of silly. The reason why I was getting this problem is because I set my umask to be nonpermissive by default. Because my umask was nonpermissive when I sudoed into root to install Rust my umask was orred with roots, and so Rust was installed with nonpermissive permissions (meaning I couldn't read from them as a normal user.) The problem was on my side, and I fixed it by changeing the sudo configuration to be more permissive by default.

@ibukanov
Copy link
Contributor

I was hit by the same issue. Note that despite 007 as umask sudo make install still managed to set proper permissions for most of the files as its use install and similar commands. I suspect the problem comes with explicit mkdir that has not set the permissions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants