# Arm32/v7 armhf support discontinue
**URL:** https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399
**Category:** Internals & Design
**Tags:** question
**Created:** [September 28, 2020, 11:43am UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399 "2020-09-28T11:43:48Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@rro](https://discourse.julialang.org/u/rro)
#### Post date: [September 28, 2020, 11:43am UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399/1 "2020-09-28T11:43:48Z")
Hi all,
I use Julia on a Docker container which is running on Raspberry Pi 3.
Till now I have cross-compiled our company application using Julia 1.4.1 and it was perfectly working if I specified the cpu target armv8-a.
Docker build: `docker buildx build --platform linux/armhf --load -t $tag .`
Julia line in Dockerfile: RUN julia -e `using PackageCompiler; create_sysimage([:TOML, :DSP], replace_default=true, cpu_target="armv8-a", precompile_execution_file="precompile.jl"); `
A couple of days ago I moved to the new Julia 1.5.2 and the cross-compilation failed. I did not notice that the arm32/v7 is not supported anymore. What are the reasons that made the support for arm32 discontinue?
Anyone found a way to cross-compile for Raspberry Pi?
Thank you!
---
### Author:  [@non-Jedi](https://discourse.julialang.org/u/non-Jedi)
#### Post date: [September 28, 2020, 12:34pm UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399/2 "2020-09-28T12:34:35Z")
Per [the julia downloads page](https://julialang.org/downloads/#currently_supported_platforms), armv7 is “Tier 3” support which means:
> Julia may or may not build. If it does, it is unlikely to pass tests. Binaries may be available in some cases. When they are, they should be considered experimental. Ongoing support is dependent on community efforts.
Looks like armv7 was changed from “Tier 2” to “Tier 3” in March of this year due to “build failures and other issues”.
>
>
> This shuffles a few support tiers:
>
> \* 32-bit Windows shifts from tier 1 to tie…r 2 support. This will allow to continue working on releases even if Win32 is being finicky with some tests. (This is the case for v1.4.0, with Win32 intermittently failing the Distributed tests.)
>
> \* AArch64 shifts from tier 2 to tier 1. We have CI that ensures that AArch64 builds and passes tests, and it has been doing so consistently for a while now.
>
> \* ARMv7 shifts from tier 2 to 3. We've had a number of issues on ARMv7, which have made producing release binaries quite tricky due to build failures and other issues.
---
### Author:  [@rro](https://discourse.julialang.org/u/rro)
#### Post date: [September 28, 2020, 1:14pm UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399/3 "2020-09-28T13:14:15Z")
Thank you for linking the issue. Many embedded systems are based on the armv7 architecture and thus we need to build julia ourselves, or change the embedded system and discontinue the old hardware.
Before doing anything, I’d like to understand the build failures or library issues. Any more information on the traps? So I save time getting out of…
Thanks!
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [September 28, 2020, 1:37pm UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399/4 "2020-09-28T13:37:25Z")
I would suggest asking in that PR. Also, if it’s “only” a matter of someone digging into various issues and you are willing to help out, perhaps it could be brought back to Tier 2 when they are resolved.
---
### Author:  [@yuyichao](https://discourse.julialang.org/u/yuyichao)
#### Post date: [September 28, 2020, 3:01pm UTC](https://discourse.julialang.org/t/arm32-v7-armhf-support-discontinue/47399/5 "2020-09-28T15:01:06Z")
The build has already been fixed. However, the compiler (and possibly ccache) on the buildbot is having some problems.