|Number of watchers on Github||10347|
|Number of open issues||2525|
|Average time to close an issue||about 20 hours|
|Average time to merge a PR||1 day|
|Open pull requests||686+|
|Closed pull requests||114+|
|Last commit||8 months ago|
|Repo Created||over 7 years ago|
|Repo Last Updated||8 months ago|
|Organization / Author||julialang|
|Do you use julia? Leave a review!|
|View open issues (2525)|
|View julia activity|
|View on github|
|Latest Open Source Launches|
Trendy new open source projects in your inbox! View examples
Julia is a high-level, high-performance dynamic language for technical computing. The main homepage for Julia can be found at julialang.org. This is the GitHub repository of Julia source code, including instructions for compiling and installing Julia, below.
New developers may find the notes in CONTRIBUTING helpful to start contributing to the Julia codebase.
Julia is built and tested regularly on the following platforms:
|Operating System||Architecture||CI||Binaries||Support Level|
|Linux 2.6.18+||x86-64 (64-bit)||Official|
|ARM v7 (32-bit)||Official|
|ARM v8 (64-bit)||Official|
|macOS 10.8+||x86-64 (64-bit)||Official|
|Windows 7+||x86-64 (64-bit)||Official|
|FreeBSD 11.0+||x86-64 (64-bit)||Community|
All systems marked with for CI are tested using continuous integration for every commit. Systems with for binaries have official binaries available on the downloads page and are tested regularly. The PTX backend needs a source build and the CUDAnative.jl package. The systems listed here with neither CI nor official binaries are known to build and work, but ongoing support for those platforms is dependent on community efforts. It's possible that Julia will build and work on other platforms too, and we're always looking to better our platform coverage. If you're using Julia on a platform not listed here, let us know!
First, make sure you have all the required dependencies installed. Then, acquire the source code by cloning the git repository:
git clone git://github.com/JuliaLang/julia.git
(If you are behind a firewall, you may need to use the
https protocol instead of the
git config --global url."https://".insteadOf git://
Be sure to also configure your system to use the appropriate proxy settings, e.g. by setting the
By default you will be building the latest unstable version of Julia. However, most users should use the most recent stable version of Julia, which is currently the
0.6 series of releases. You can get this version by changing to the Julia directory and running
git checkout v0.6.2
make to build the
julia executable. To perform a parallel build, use
make -j N and supply the maximum number of concurrent processes. (See Platform Specific Build Notes for details.)
When compiled the first time, it will automatically download and build its external dependencies.
This takes a while, but only has to be done once. If the defaults in the build do not work for you, and you need to set specific make parameters, you can save them in
Make.user. The build will automatically check for the existence of
Make.user and use it if it exists.
Building Julia requires 1.5GiB of disk space and approximately 700MiB of virtual memory.
For builds of julia starting with 0.5.0-dev, you can create out-of-tree builds of Julia by specifying
make O=<build-directory> configure on the command line. This will create a directory mirror, with all of the necessary Makefiles to build Julia, in the specified directory. These builds will share the source files in Julia and
deps/srccache. Each out-of-tree build directory can have its own
Make.user file to override the global
Make.user file in the top-level folder.
If you need to build Julia on a machine without internet access, use
make -C deps getall to download all the necessary files. Then, copy the
julia directory over to the target environment and build with
Note: The build process will fail badly if any of the build directory's parent directories have spaces or other shell meta-characters such as
: in their names (this is due to a limitation in GNU make).
Once it is built, you can run the
julia executable using its full path in the directory created above (the
julia directory). To run julia from anywhere you can:
echo "alias julia='/path/to/install/folder/bin/julia'" >> ~/.bashrc && source ~/.bashrc), or
add a soft link to the
julia executable in the
julia directory to
/usr/local/bin (or any suitable directory already in your path), or
julia directory to your executable path for this shell session (in
export PATH="$(pwd):$PATH" ; in
set path= ( $path $cwd ) ), or
julia directory to your executable path permanently (e.g. in
Make.user and then run
make install. If there is a version of Julia already installed in this folder, you should delete it before running
Now you should be able to run Julia like this:
If everything works correctly, you will see a Julia banner and an interactive prompt into which you can enter expressions for evaluation. (Errors related to libraries might be caused by old, incompatible libraries sitting around in your PATH. In this case, try moving the
julia directory earlier in the PATH).
Your first test of Julia determines whether your build is working properly. From the UNIX/Windows command prompt inside
julia source directory, type
make testall. You should see output that lists a series of running tests;
if they complete without error, you should be in good shape to start using Julia.
You can read about getting started in the manual.
If you are building a Julia package for distribution on Linux, OS X, or Windows, take a look at the detailed notes in DISTRIBUTING.md.
If you have previously downloaded
git clone, you can update the
existing source tree using
git pull rather than starting anew:
cd julia git pull && make
Assuming that you had made no changes to the source tree that will conflict with upstream updates, these commands will trigger a build to update to the latest version.
*** This error is usually fixed by running 'make clean'. If the error persists, try 'make cleanall' ***
As described, running
make clean && make is usually sufficient.
Occasionally, the stronger cleanup done by
make cleanall is needed.
make targets exist to help wipe the existing build of a
dependency. For example,
make -C deps clean-llvm will clean out the
existing build of
llvm so that
llvm will be rebuilt from the
downloaded source distribution the next time
make is called.
make -C deps distclean-llvm is a stronger wipe which will also delete
the downloaded source distribution, ensuring that a fresh copy of the
source distribution will be downloaded and that any new patches will be
applied the next time
make is called.
b. To delete existing binaries of
julia and all its dependencies,
./usr directory in the source tree.
If you've updated OS X recently, be sure to run
xcode-select --install to update the command line tools.
Otherwise, you could run into errors for missing headers and libraries, such as
ld: library not found for -lcrt1.10.6.o.
If you've moved the source directory, you might get errors such as
CMake Error: The current CMakeCache.txt directory ... is different than the directory ... where CMakeCache.txt was created., in which case you may delete the offending dependency under
In extreme cases, you may wish to reset the source tree to a pristine state. The following git commands may be helpful:
git reset --hard #Forcibly remove any changes to any files under version control git clean -x -f -d #Forcibly remove any file or directory not under version control
To avoid losing work, make sure you know what these commands do before you
git will not be able to undo these changes!
Julia does not install anything outside the directory it was cloned into. Julia can be completely uninstalled by deleting this directory. Julia packages are installed in
~/.julia by default, and can be uninstalled by deleting
LDFLAGS, putting the library directory into the environment variable
LD_LIBRARY_PATH(at both compile and run time) also works.
Julia can be built for a non-generic architecture by configuring the
ARCH Makefile variable. See the appropriate section of
Make.inc for additional customization options, such as
For example, to build for Pentium 4, set
MARCH=pentium4 and install the necessary system libraries for linking. On Ubuntu, these may include lib32gfortran-6-dev, lib32gcc1, and lib32stdc++6, among others.
You can also set
MARCH=native for a maximum-performance build customized for the current machine CPU.
The julia-deps PPA contains updated packages for Julia dependencies if you want to use system libraries instead of having them downloaded and built during the build process. See System Provided Libraries.
On RHEL/CentOS 6 systems, the default compiler (
gcc 4.4) is too old to build Julia.
Install or contact your systems administrator to install a more recent version of
gcc. The Scientific Linux Developer Toolset works well.
|OpenBLAS build failure||Set one of the following build options in
If you get an error that looks like
|Illegal Instruction error||Check if your CPU supports AVX while your OS does not (e.g. through virtualization, as described in this issue).|
You need to have the current Xcode command line utilities installed: run
xcode-select --install in the terminal.
You will need to rerun this terminal command after each OS X update, otherwise you may run into errors involving missing libraries or headers.
You will also need a 64-bit gfortran to compile Julia dependencies. The gfortran-4.7 (and newer) compilers in Brew, Fink, and MacPorts work for building Julia.
Clang is now used by default to build Julia on OS X 10.7 and above. On OS X 10.6, the Julia build will automatically use
On current systems, we recommend that you install the command line tools as described above. Older systems do not have a separate command line tools package from Apple, and will require a full Xcode install. On these, you will need at least Xcode 4.3.3. In Xcode prior to v5.0, you can alternatively go to Preferences -> Downloads and select the Command Line Utilities. These steps will ensure that clang v3.1 is installed, which is the minimum version of
clang required to build Julia.
If you have set
DYLD_LIBRARY_PATH in your
.bashrc or equivalent, Julia may be unable to find various libraries that come bundled with it. These environment variables need to be unset for Julia to work.
If you see build failures in OpenBLAS or if you prefer to experiment, you can use the Apple provided BLAS in vecLib by building with
USE_SYSTEM_BLAS=1. Julia does not use the Apple provided LAPACK, as it is too old.
When building Julia, or its dependencies, libraries installed by third party package managers can redirect the compiler to use an incompatible version of the software it is looking for. One example of this happening is when a piece of software called the
linker gives an error involving
Undefined symbols. If that happens, you can usually figure out what software package is causing the error from the names in the error text. This sort of error can be bypassed by, temporarily, uninstalling the offending package. If the offending package cannot be uninstalled by itself, it may be possible to just uninstall the development headers (for example: a package ending in
-dev in Fink).
Clang is the default compiler on FreeBSD 11.0-RELEASE and above.
The remaining build tools are available from the Ports Collection, and can be installed using
pkg install git gcc gmake cmake.
To build Julia, simply run
gmake must be used rather than
make on FreeBSD corresponds to the incompatible BSD Make rather than GNU Make.)
It's important to note that the
USE_SYSTEM_* flags should be used with caution on FreeBSD.
This is because many system libraries, and even libraries from the Ports Collection, link to the system's
or to another library which links to the system
This library declares its GCC version to be 4.6, which is too old to build Julia, and conflicts with other libraries when linking.
Thus it is highly recommended to simply allow Julia to build all of its dependencies.
If you do choose to use the
USE_SYSTEM_* flags, note that
/usr/local is not on the compiler path by default, so you may need
CPPFLAGS=-I/usr/local/include to your
Make.user, though doing so may interfere with
Some known issues on FreeBSD are:
The x86 architecture does not support threading due to lack of compiler runtime library support, so you may need to
JULIA_THREADS=0 in your
Make.user if you're on a 32-bit system.
Pkg test suite segfaults on FreeBSD 11.1, likely due to a change in FreeBSD's default handling of stack guarding.
See issue #23328 for more information.
In order to build Julia on Windows, see README.windows.
Julia can be developed in an isolated Vagrant environment. See the Vagrant README for details.
Building Julia requires that the following software be installed:
libgit2correctly, especially for proxy support.
Julia uses the following external libraries, which are automatically downloaded (or in a few cases, included in the Julia source repository) and then compiled from source the first time you run
Package maintainers will typically want to make use of system libraries where possible. Please refer to the above version requirements and additional notes below. A list of maintained Julia packages for various platforms is available at https://julialang.org/downloads/platform.html.
If you already have one or more of these packages installed on your system, you can prevent Julia from compiling duplicates of these libraries by passing
make or adding the line to
Make.user. The complete list of possible flags can be found in
Please be aware that this procedure is not officially supported, as it introduces additional variability into the installation and versioning of the dependencies, and is recommended only for system package maintainers. Unexpected compile errors may result, as the build system will do no further checking to ensure the proper packages are installed.
The most complicated dependency is LLVM, for which we require version 3.9 with some additional patches from upstream (LLVM is not backward compatible). For packaging Julia, we recommend either:
deps/llvm.mk, and the patches themselves are in
llvm-symver-jlprefix.patch), which should not be applied to a system LLVM.
Using an unpatched or different version of LLVM will result in errors and/or poor performance. Though Julia can be built with newer LLVM versions, support for this should be regarded as experimental and not suitable for packaging.
Julia uses a custom fork of libuv. It is a small dependency, and can be safely bundled in the same package as Julia, and will not conflict with the system library. Julia builds should not try to use the system libuv.
As a high-performance numerical language, Julia should be linked to a multi-threaded BLAS and LAPACK, such as OpenBLAS or ATLAS, which will provide much better performance than the reference
libblas implementations which may be default on some systems.
SuiteSparse is a special case, since it is typically only installed as a static library, while
USE_SYSTEM_SUITESPARSE=1 requires that it is a shared library. Running the script
contrib/repackage_system_suitesparse4.make will copy your static system SuiteSparse installation into the shared library format required by Julia.
make USE_SYSTEM_SUITESPARSE=1 will then use the SuiteSparse that has been copied into Julia's directory, but will not build a new SuiteSparse library from scratch.
To build Julia using the Intel compilers (icc, icpc, ifort), and link against the MKL BLAS and LAPACK libraries, first make sure you have a recent version of the compiler suite (version 15 or later).
For a 64-bit architecture, the environment should be set up as follows:
# bash source /path/to/intel/bin/compilervars.sh intel64
Add the following to the
USEICC = 1 USEIFC = 1 USE_INTEL_MKL = 1 USE_INTEL_LIBM = 1
It is highly recommended to start with a fresh clone of the Julia repository.
The Julia source code is organized as follows:
base/ source code for the Base module (part of Julia's standard library) stdlib/ source code for other standard library packages contrib/ editor support for Julia source, miscellaneous scripts deps/ external dependencies doc/src/manual source for the user manual doc/src/stdlib source for standard library function reference src/ source for Julia language core test/ test suites ui/ source for various front ends usr/ binaries and shared libraries loaded by Julia's standard libraries
If you would rather not compile the latest Julia from source, platform-specific tarballs with pre-compiled binaries are also available for download.
You can either run the
julia executable using its full path in the directory created above, or add that directory to your executable path so that you can run the Julia program from anywhere (in the current shell session):
Now you should be able to run Julia like this:
On Windows, double-click
If everything works correctly, you will see a Julia banner and an interactive prompt into which you can enter expressions for evaluation. You can read about getting started in the manual.
Note: Although some system package managers provide Julia, such installations are neither maintained nor endorsed by the Julia project. They may be outdated and/or unmaintained. We recommend you use the official Julia binaries instead.
Currently, Julia editing mode support is available for a number of
editors. While Julia modes for
Sublime Text, and
Vim have their own repos,
others such as Textmate, Notepad++, and Kate, are in
Two major IDEs are supported for Julia: Juno which is based on Atom and julia-vscode based on VS Code. A Jupyter notebooks interface is available through IJulia. The Sublime-IJulia plugin enables interaction between IJulia and Sublime Text.
In the terminal, Julia makes great use of both control-key and meta-key bindings. To make the meta-key bindings more accessible, many terminal emulator programs (e.g.,
xterm, etc.) allow you to use the alt or option key as meta. See the section in the manual on the Julia REPL for more details.