Closed foobazjo closed 2 years ago
UPDATE: I've renamed my machine from asrock_rack/asrock_rack_e3c246d2i to asrock_rack/e3c246d2i, I'm no longer having the gpg path len issue but all those build/images folder are not being created for me.
I'm using the ONIE Debian 10 build env from DUE and tag 2021.11. Not sure what I'm doing wrong.
UPDATE2: It's working fine now, it was all related to not using (and knowing) about MACHINEROOT=../machine/asrock_rack, initially using MACHINE=asrock_rack/asrock_rack_e3c246d2i, was working until the part in the Makefiles that was removing and mkdir -p the various image folders.
After analyzing the error below, it looks like _/home/silvercro/sandbox/onie/build/images/asrockrack/ was not created for some reason.
Just for debuging the issue I went ahead and created it:
silvercro@due-onie-build-debian-10:~/sandbox/onie/build-config$ mkdir -p /home/silvercro/sandbox/onie/build/images/asrock_rack/
Resumed building:
Note that my machine directory is a sub-directory (like other vendors with multiple models):
Directory base absolute path [ /home/silvercro/sandbox/onie/build/images/asrock_rack/asrock_rack_e3c246d2i-r0.vmlinuz ] has [ 87 ] characters.
Looks like my machine path is too long and gpg is not happy. Was there anything in the build process that prevented creating my directory in the first place with a silent error and it's only visible at the end of the build process when it's trying to move things in the images directory?
asrock_rack/asrock_rack_e3c246d2i is a machine I created by copying kvm_x86_64.