SpiroCx
commented
8 months ago I had the same error compiling on Ubuntu 22.04. All of these failed: build.sh milkv-duo, build.sh milkv-duo-light, step-by-step duo/duo-light, docker duo/duo-light.
I tried them all again after checking out tag Duo-V1.0.9 (commit c737560cc). Same errors, so I checked out develop again (commit 1d878b3d9).
I decided to focus on the docker build. I don't know what the proper solution is but I got it going.
The main way to find the workaround was
- replace that line 605 of build/Makefile (as mentioned in the error message) with "make -j1 -C $(BR_DIR)"
- install strace into the container and use it to take a closer look at "make br-rootfs-pack"
Removing the brmake wrapper (brmake -> make) and running make with make SHELL='sh -x' gives more info. This shows there a problem with a fakeroot call.
You can verify this path to fakeroot.so problem by running the fakeroot line separately and adding strace:
export PATH="/home/work/buildroot-2021.05/output/milkv-duo-lite_musl_riscv64/host/bin:/home/work/buildroot-2021.05/output/milkv-duo-lite_musl_riscv64/host/sbin:/home/work/host-tools/gcc/riscv64-linux-musl-x86_64/bin:/home/work/host-tools/gcc/riscv64-linux-x86_64/bin:/home/work/host-tools/gcc/riscv64-elf-x86_64/bin:/home/work/host-tools/gcc/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-elf/bin:/home/work/host-tools/gcc/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf/bin:/home/work/host-tools/gcc/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/work/host-tools/gcc/arm-cvitek-linux-uclibcgnueabihf/bin"
export FAKEROOTDONTTRYCHOWN=1
strace /home/work/buildroot-2021.05/output/milkv-duo-lite_musl_riscv64/host/bin/fakeroot -- /home/work/buildroot-2021.05/output/milkv-duo-lite_musl_riscv64/build/buildroot-fs/ext2/fakeroot 2>&1 | grep libfakeroot.so In the docker container, at least, the problem is that the external paths are being used inside the container. I needed to do this to get the docker build working:
replicate base dir inside docker container (docker exec -it duodocker /bin/bash):
mkdir -p /home/<host path>/duo-buildroot-sdk/
cd /home/<host path>/duo-buildroot-sdk/
ln -s /home/work/buildroot-2021.05 .
ln -s /home/work/host-tools .- For example, in my case, I needed:
mkdir -p /home/spiro/_milk-v/duo-buildroot-sdk/... - I guess it would work if I replicate the container path in the host - create a user called work (or at least path /home/work/) and start the process (git clone) in /home/work
- I am wondering also if this entire path problem only exists because I tried the one-click build in the host machine before trying the docker build (which ran the 2 path setup scripts). I will try a clean build soon.
NOTE: I also did these 2 things in the container which may be useless, or may be significant:
apt install kmod
apt remove fakeroot
- the first was because I noticed an error message regarding missing util depmod.
- the second was because there is a fakemod in the sdk and one of my guesses was that it may be using the wrong one.
I can confirm now that both of these commands work outside the docker container (running on the host machine):
docker exec -it duodocker /bin/bash -c "cd /home/work && cat /etc/issue && ./build.sh milkv-duo-lite"
docker exec -it duodocker /bin/bash -c "cd /home/work && cat /etc/issue && ./build.sh milkv-duo"and you get your images in: /duo-buildroot-sdk/out/
- milkv-duo-lite.img
- milkv-duo.img
Bender1983
MarkMLl
informatik-bks
PJ5168
LevitatingBusinessMan
zzhelezc
2024-03-09T20:23:57 >>> linux-firmware 20201022 Installing to images directory 2024-03-09T20:23:58 >>> subversion 1.14.1 Installing to target Done in 14min 01s (error code: 2) make: *** [Makefile:605: br-rootfs-pack] Error 2 Error: Build board milkv-duo failed! root@74ef18797463:/home/work#