-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Broken install when configured with a custom --prefix #16733
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
Comments
cc me. I think I've been running into this problem without realizing it. |
So not sure what's going on. If I |
Progress! |
Alright something is definitely messed up with my machine. I was able to install rust with a custom prefix just fine on another Mac. I'll close this for now, it is definitely my problem. Sorry for the bother. |
@jasonroelofs out of curiosity did the other machine also have Homebrew? Just curious about own past observations |
The other machine did not have homebrew, but for this situation specifically, I think it came down to a simple mis-type that ensured my
vs
Very important distinction! |
@jasonroelofs Thanks for the last comment. I had same problem and could fix by adding |
I'm trying to build Rust from source on Mac OS X 10.9 installing it to a custom prefix (
/opt/rust
because/usr/local/
is managed by homebrew). I have successfully donebrew install rust --HEAD
, which works with the defaults and gives me a valid Rust install. However, my install to/opt/rust
leads to an inability to find library files (and oddly is looking for stage1 library builds).Steps to get to where I am
Installation succeeds but running the installed
rustc
fails.Following other tickets found here, I made sure to set my
DYLD_LIBRARY_PATH
and myLD_LIBRARY_PATH
for safe measure to the custom install directory.It seems that there's something wrong with the build process when using a custom prefix, such that the system doesn't take the final step of ensuring the binary will look for the various libraries in their installed locations.
In what may be a further help, the build system seems to be installing the binary from
stage2
which itself is linked back to thestage1
libraries.My build's
stage3
directory is nothing but empty folders.Thanks!
The text was updated successfully, but these errors were encountered: