Closed VielLosero closed 3 years ago
Don't know what exactly went wrong with the init script, but it looks like it didn't add the meta-qcom layer to your settings, can you check if all layers defined in init.sh have been populated in yocto/build/conf/bblayers.conf?
Recently I started moving to yocto release 3.2, if the clone is not recent, you might have a broken tree. If in doubt, do a git pull, completely erase the yocto folder (if you didn't make any changes to the tree, and rerun init.sh to recreate the structure)
[v@arcadia build]$ bitbake-layers show-layers
NOTE: Starting bitbake server...
layer path priority
==========================================================================
meta /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk-bkp/yocto/meta 5
meta-poky /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk-bkp/yocto/meta-poky 5
meta-yocto-bsp /home/v/data/olimex/usb-glink/new_kernel_and_bootloader/pinephone_modem_sdk-bkp/yocto/meta-yocto-bsp 5
[v@arcadia build]$
U right seems the firewall blocks something. From a fresh init (without firewall) it works great. I need to disable firewall to build as well because yocto download lot of files with no common ports 80 or 443. Sorry for the inconvenience , and thanks a lot.
Closing the issue since it worked, if anything else fails please let me know
is there a layer missing? maybe I missed something ... any help is appreciated thanks