Skip to content
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.

Sign up for GitHub

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

Jump to bottom

switch to specifying the relative location of the sysimg directly #16

Merged
merged 1 commit into from
Sep 1, 2014
Merged

switch to specifying the relative location of the sysimg directly #16

merged 1 commit into from
Sep 1, 2014

Conversation

jakebolewski
Copy link
Contributor

This was brought up on the julia-users mailing list: https://groups.google.com/forum/#!topic/julia-users/8GSHVuDjkC4

@stevengj
Copy link
Member

stevengj commented Sep 1, 2014

Why is jl_init not doing the right thing here?

jakebolewski added a commit that referenced this pull request Sep 1, 2014
@jakebolewski
Merge pull request #16 from JuliaLang/jcb/relpathfix
b0df4d7 
switch to specifying the relative location of the sysimg directly
@jakebolewski jakebolewski merged commit b0df4d7 into master Sep 1, 2014
@stevengj
Copy link
Member

stevengj commented Sep 1, 2014

See also JuliaLang/julia#5045.

@jakebolewski jakebolewski deleted the jcb/relpathfix branch September 1, 2014 18:23
@jakebolewski
Copy link
Contributor Author

jl_init has a hard-coded relative path that is set during the build process from source. The whole relative path thing is awkward, we should just specify the two paths we need to initialize Julia directly.

@stevengj
Copy link
Member

stevengj commented Sep 2, 2014

The point is, where do we get the second path? If julia knows the correct path, it should use this path in jl_init. And if julia doesn't know the path, then the sysimg is broken for julia itself and should be fixed there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jakebolewski @stevengj