golang: Makefile:380: *** go-bootstrap cannot be installed on linux/arm64. Stop.

[alex9434]

Maintainer: @jefferyto @kuoruan
Environment: aarch64, Raspberry Pi 4B, Snapshot
Build system: Linux debian-buster-64 4.19.118-v8+ #1311 SMP PREEMPT Mon Apr 27 14:32:38 BST 2020 aarch64 GNU/Linux

Description:
Package docker-ce does not build on Debian 10 Aarch64. error message:

make[3]: Leaving directory '/home/pi/Downloads/openwrt/feeds/packages/utils/cgroupfs-mount'
time: package/feeds/packages/cgroupfs-mount/compile#0.50#0.54#1.03
make[3]: Entering directory '/home/pi/Downloads/openwrt/feeds/packages/lang/golang/golang'
Makefile:380: *** go-bootstrap cannot be installed on linux/arm64.  Stop.
make[3]: Leaving directory '/home/pi/Downloads/openwrt/feeds/packages/lang/golang/golang'
time: package/feeds/packages/golang/host-compile#0.19#0.06#0.28
make[2]: *** [package/Makefile:111: package/feeds/packages/golang/host/compile] Error 2
make[2]: Leaving directory '/home/pi/Downloads/openwrt'
make[1]: *** [package/Makefile:107: /home/pi/Downloads/openwrt/staging_dir/target-aarch64_cortex-a72_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/home/pi/Downloads/openwrt'
make: *** [/home/pi/Downloads/openwrt/include/toplevel.mk:235: world] Error 2

[jefferyto]

1. Install Go on your build system, either using your distro’s packages or from golang.org.
2. In make menuconfig, find the “ External bootstrap Go root directory” option for the golang package and enter the path for the working Go tree installed in the previous step.
3. Build as normal.

[jefferyto]

If you installed Go using the Debian package, then the working Go tree path would be /usr/lib/go-1.11 (or /usr/lib/go-1.14 if you are using buster-backports).

The instructions I provided should have resolved your issue. Please comment if you are able to build Go/Docker successfully or if you have encountered additional issues (or if the instructions were unclear).

Also, in the future please ping (@ mention) only the maintainer of the package (listed in the package's Makefile), not every contributor who has committed a change for the package. Pinging everyone does not lead to your issue being resolved faster, it leads to people being less willing to help you.

[alex9434]

Hi @jefferyto, I am just in the process of compiling with your suggestions. Thank you for your help and the very quick answer! Really appreciated.

Unfortunately I just run into another issue with runc:
openwrt/build_dir/target-aarch64_cortex-a72_musl/runc-1.0.0-rc10/.go_work/build/src/github.com/opencontainers/runc: No such file or directory. Stop.

Would you happen to know how to fix that? I am trying to build an image from master for Raspberry Pi 4 including docker-ce.

Apologies for tagging everybody. I was trying to follow the instruction from the ticket that asked to look at the history of the makefile. Unfortunately I incorrectly took you both for maintainers. I was not trying to be 'pushy'. Will keep that in mind moving forward. Thank you for your clarification!

[jefferyto]

That looks like an issue with the runc package. Can you create a new issue for runc and include the full build/make log?

[alex9434]

Hi @jefferyto I have seen that you are also maintainer of rung. I solved the issue above with the following recommendation:

https://forum.openwrt.org/t/runc-and-containerd-compilation-fails/60572

(comment out #rm -f $(STAMP_BUILT). Just as an FYI in case you want to fix that upstream. Thank you again for your support.

[jefferyto]

I'm glad you were able to find a fix.

Just to clear things up: I am not the maintainer of runc; the maintainer is Gerard Ryan. You need to look inside the package Makefile to find the maintainer's name. The comment in the issue template tells you how to find the GitHub username for the maintainer.

[geopenwu]

1. Install Go on your build system, either using your distro’s packages or from golang.org.
2. In make menuconfig, find the “ External bootstrap Go root directory” option for the golang package and enter the path for the working Go tree installed in the previous step.
3. Build as normal.

Thank you! I had the same issue, and resolved it with this instruction.