xeroxss Posted September 7, 2022 Posted September 7, 2022 Hi everyone, I'm trying to compile an image for Orange Pi One with the default config for desktop - but I'm running on box86 error, unable to locate box86 then the process terminates. Do I need to install it first from here >>> https://github.com/ptitSeb/box86 before I can make a successful image compile? - I also tried compiling just the kernel and my virtual box setup works just fine outputting compiled deb files.
Igor Posted September 7, 2022 Posted September 7, 2022 1 hour ago, xeroxss said: Hi everyone, I'm trying to compile an image for Orange Pi One with the default config for desktop Hi stranger. Start here: https://www.armbian.com/bugs/ and here https://docs.armbian.com/Developer-Guide_Build-Preparation/ Then search forums. Logs are located in output/debug. This is what you need to check 1st. This https://github.com/armbian/build/actions/workflows/build-all-desktops.yml tells us that 20 hours ago installation of all possible desktops worked. Tried local build: no issues. It could be some network related problem on your side. Try again.
xeroxss Posted September 8, 2022 Author Posted September 8, 2022 Hi @Igor I tried your suggestion to look at the network errors, so I fixed the mirror that are causing some downloads to fail however I try running it 2 times with the same result I thought selecting and unselecting build with 3d options enabled will fix the issue, however I got the same error twice the compiler is still looking for box86 then terminates, looking at the all desktop logs build from your link It looks like it is the same error related to my issue 4 days ago here >>> https://github.com/armbian/build/actions/runs/2986004306 I check out my build script from armbian master branch. My build machine is also on Ubuntu Mate running on Virtualbox. https://dev.dw1zws.com/downloads/debug/box86-3error.JPG
Igor Posted September 8, 2022 Posted September 8, 2022 12 minutes ago, xeroxss said: looking at the all desktop logs build from your link That link proves that problem was fixed, but network issues and bugs in 3rd party components can rise up at any time ... This commit https://github.com/armbian/build/pull/4163 could contribute to the problem you were facing. Another possible problem are APT_CATCHER bugs, another Qemu bugs, ... Documentation is your first stop.
xeroxss Posted September 10, 2022 Author Posted September 10, 2022 Hi @Igor, thanks for pointing me to the direction, I can confirm that the build works fine following the documentation for build verbatim on my virtualbox install. 1
Recommended Posts