From 8b43d20537c288e7a0fef956ab1b3f7797f07b5f Mon Sep 17 00:00:00 2001 From: Mao Zeng Date: Mon, 16 Sep 2024 14:19:01 +0100 Subject: [PATCH 1/4] Comment on julia installation location with juliaup installer --- website/user_gettingstarted.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/user_gettingstarted.md b/website/user_gettingstarted.md index b5b6214..0dcd53f 100644 --- a/website/user_gettingstarted.md +++ b/website/user_gettingstarted.md @@ -23,7 +23,7 @@ Getting started with Julia on a new cluster can sometimes be a challenge. Below When starting on a new HPC cluster the first thing you should do is figure out if there is a pre-configured Julia module ([Lmod module](https://lmod.readthedocs.io/en/latest/010_user.html)) available on the cluster. To that end, `module key julia` or `module spider julia` might be helpful commands. -If there is no Julia module available that you can load, you should download and use the regular, precompiled Julia binaries. We strongly recommend to use [juliaup](https://github.com/JuliaLang/juliaup) for this. Alternatively, you can also manually download the binaries directly [from the website](https://julialang.org/downloads/). In any case, you should generally **not** build Julia from source (unless you have a very good reason). +If there is no Julia module available that you can load, you should download and use the regular, precompiled Julia binaries. We strongly recommend to use [juliaup](https://github.com/JuliaLang/juliaup) for this. The installation path of the `julia` executable will be added to your `~/.bashrc` by `juliaup`. If the job scheduler does not load `.bashrc` in non-interactive jobs, you can find out the installation path by starting the Julia REPL and type `Sys.BINDIR`. Alternatively, you can also manually download the binaries directly [from the website](https://julialang.org/downloads/). In any case, you should generally **not** build Julia from source (unless you have a very good reason). Note that you **do not** need root privileges. Julia, and its packages, works great without special permissions in user space. From e8ec863c546b30aeb6e0333e414853ffacc890ae Mon Sep 17 00:00:00 2001 From: Mao Zeng Date: Mon, 16 Sep 2024 15:14:41 +0100 Subject: [PATCH 2/4] Revert "Comment on julia installation location with juliaup installer" This reverts commit 8b43d20537c288e7a0fef956ab1b3f7797f07b5f. --- website/user_gettingstarted.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/user_gettingstarted.md b/website/user_gettingstarted.md index 0dcd53f..b5b6214 100644 --- a/website/user_gettingstarted.md +++ b/website/user_gettingstarted.md @@ -23,7 +23,7 @@ Getting started with Julia on a new cluster can sometimes be a challenge. Below When starting on a new HPC cluster the first thing you should do is figure out if there is a pre-configured Julia module ([Lmod module](https://lmod.readthedocs.io/en/latest/010_user.html)) available on the cluster. To that end, `module key julia` or `module spider julia` might be helpful commands. -If there is no Julia module available that you can load, you should download and use the regular, precompiled Julia binaries. We strongly recommend to use [juliaup](https://github.com/JuliaLang/juliaup) for this. The installation path of the `julia` executable will be added to your `~/.bashrc` by `juliaup`. If the job scheduler does not load `.bashrc` in non-interactive jobs, you can find out the installation path by starting the Julia REPL and type `Sys.BINDIR`. Alternatively, you can also manually download the binaries directly [from the website](https://julialang.org/downloads/). In any case, you should generally **not** build Julia from source (unless you have a very good reason). +If there is no Julia module available that you can load, you should download and use the regular, precompiled Julia binaries. We strongly recommend to use [juliaup](https://github.com/JuliaLang/juliaup) for this. Alternatively, you can also manually download the binaries directly [from the website](https://julialang.org/downloads/). In any case, you should generally **not** build Julia from source (unless you have a very good reason). Note that you **do not** need root privileges. Julia, and its packages, works great without special permissions in user space. From 76412d2bac468645438e4efdbdceed22f5c9d87d Mon Sep 17 00:00:00 2001 From: Mao Zeng Date: Mon, 16 Sep 2024 15:18:59 +0100 Subject: [PATCH 3/4] Add juliaup installation path comment to FAQ. --- website/user_faq.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/website/user_faq.md b/website/user_faq.md index fdbfb17..57d328d 100644 --- a/website/user_faq.md +++ b/website/user_faq.md @@ -25,6 +25,12 @@ Yes, absolutely. You **do not** need root privileges to install Julia and its pa [⤴ _**back to Content**_](#content) +## Julia installed from juliaup not found in a non-interactive job + +The installation path of the `julia` executable will be added to your `~/.bashrc` by [juliaup](https://github.com/JuliaLang/juliaup). If the job scheduler does not load `.bashrc` in non-interactive jobs, you can find out the installation path by starting the Julia REPL and type `Sys.BINDIR`. + +[⤴ _**back to Content**_](#content) + ## Where should I put the Julia depot? Ideally, you should set `JULIA_DEPOT_PATH` to point to a place with the following properties: @@ -136,4 +142,4 @@ By default, Julia uses many parallel tasks during precompilation. On the login n Yes, at least for CUDA.jl. See [this part](https://cuda.juliagpu.org/stable/installation/overview/#Precompiling-CUDA.jl-without-CUDA) of the CUDA.jl documentation. -[⤴ _**back to Content**_](#content) \ No newline at end of file +[⤴ _**back to Content**_](#content) From 8e5d7f3dd8f2e5c3d313ea2d928c0d9fcf987da8 Mon Sep 17 00:00:00 2001 From: Mao Zeng Date: Mon, 16 Sep 2024 17:04:52 +0100 Subject: [PATCH 4/4] Make text clearer. Co-authored-by: Carsten Bauer --- website/user_faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/user_faq.md b/website/user_faq.md index 57d328d..645fe91 100644 --- a/website/user_faq.md +++ b/website/user_faq.md @@ -27,7 +27,7 @@ Yes, absolutely. You **do not** need root privileges to install Julia and its pa ## Julia installed from juliaup not found in a non-interactive job -The installation path of the `julia` executable will be added to your `~/.bashrc` by [juliaup](https://github.com/JuliaLang/juliaup). If the job scheduler does not load `.bashrc` in non-interactive jobs, you can find out the installation path by starting the Julia REPL and type `Sys.BINDIR`. +The installation path of the `julia` executable will be added to your `~/.bashrc` by [juliaup](https://github.com/JuliaLang/juliaup). If the job scheduler does not load `.bashrc` in non-interactive jobs, you must use the full path to `julia` in your job script. You can find out the full path by starting the Julia REPL and typing `Sys.BINDIR`. By default, it should be `~/.juliaup/bin/julia`. [⤴ _**back to Content**_](#content)