-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
julia uses an absolute path #11270
Comments
@andrewcooke would #11272 fix it for you? |
build directories are non-relocatable and can do all sorts of a bad things if you try. for example, any autoconf or cmake driven dependency will use the absolute path to the original location and may discard anything that it finds there. |
For the record, while I agree with Jameson, I also agree that it's a very simple thing to fix, and there's no good reason in my mind why we shouldn't make it a relative path. |
it does, but tbh i'd rather it breaks in an obvious way rather than have some weird problem as described by vtjnash. although i am a little surprised - i use autoconf quite a bit and thought it used relative paths. anyway, seems like a bad idea. sorry/thanks. andrew |
For others reading this, things that won't work are moving the directory tree, and then expecting a Things that should work are moving the
99% of the time, |
fwiw, it seems to be the handwritten Makefile in deps that is the source of the absolute paths. |
when you build julia from git, it seems that the julia command in the top level is linked to an absolute path that is equivalent to ./usr/bin/julia.
please don't do that (use an absolute path), because if someone is dumb enough to move the directory, and then build a new julia version, in a directory with the same name, all kinds of confusion can break out. yes, i am that dumb person, but i cannot see why a relative path wouldn't have sufficed.
thanks!
The text was updated successfully, but these errors were encountered: