# Julia 1.6.2 now in conda-forge

**URL:** <https://discourse.julialang.org/t/julia-1-6-2-now-in-conda-forge/67949>\
**Category:** Tooling\
**Tags:** python, conda, conda-forge\
**Created:** [September 9, 2021, 5:02pm UTC](https://discourse.julialang.org/t/julia-1-6-2-now-in-conda-forge/67949 "2021-09-09T17:02:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [September 9, 2021, 5:02pm UTC](https://discourse.julialang.org/t/julia-1-6-2-now-in-conda-forge/67949/1 "2021-09-09T17:02:40Z")

</div>

Julia 1.6.2 can now be installed via conda-forge:  
[https://anaconda.org/conda-forge/julia](https://anaconda.org/conda-forge/julia)

Note that this is a custom build for conda-forge and is not the official Julia binaries. The main difference is that it uses conda-forge binary dependencies to build Julia rather than the vendored binaries usually built via BinaryBuilder. This creates a version of Julia that may be more compatible with other conda-forge binaries than the official Julia.

The build recipe for Julia can be found in the conda-forge/julia-feedstock repository:  
[https://github.com/conda-forge/julia-feedstock/blob/master/recipe/build.sh](https://github.com/conda-forge/julia-feedstock/blob/master/recipe/build.sh)

While I anticipate this may make community support more complicated, I also hope this will make Julia more accessible to the conda-forge community.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [September 9, 2021, 6:42pm UTC](https://discourse.julialang.org/t/julia-1-6-2-now-in-conda-forge/67949/2 "2021-09-09T18:42:14Z")

</div>

> [@mkitti](#):
>
> Note that this is a custom build for conda-forge and is not the official Julia binaries. The main difference is that it uses conda-forge binary dependencies to build Julia rather than the vendored binaries usually built via BinaryBuilder. This creates a version of Julia that may be more compatible with other conda-forge binaries than the official Julia.

Is this using the patched LLVM and all of that?

---

<div class="post-metadata">

**Author:** ![mkitti](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkitti/32/12459_2.png) [@mkitti](https://discourse.julialang.org/u/mkitti)\
**Post date:** [September 9, 2021, 8:11pm UTC](https://discourse.julialang.org/t/julia-1-6-2-now-in-conda-forge/67949/3 "2021-09-09T20:11:50Z")

</div>

The conda-forge build is currently using patched LLVM:  
[https://github.com/conda-forge/julia-feedstock/blob/842571fa894766a6bc0cbc93e74db0c812ea8867/recipe/build.sh#L51](https://github.com/conda-forge/julia-feedstock/blob/842571fa894766a6bc0cbc93e74db0c812ea8867/recipe/build.sh#L51)

That’s the one dependency where I don’t think we will be able to use a generic build for. The one possibility is that conda-forge may distribute Julia’s patched LLVM at some point. The non-conda-forge binaries being used are

1. LLVM - discussed above
2. libuv - Julia’s version has diverged from upstream
3. mbedtls - This is due to some Downloads.jl issues, [https://github.com/JuliaLang/Downloads.jl/pull/114](https://github.com/JuliaLang/Downloads.jl/pull/114)
4. cls (C++ standard library) - I’m not sure about this, but I think everything needs to be linked against the same CSL.