2020-07-20 07:53 AM
I'm trying to build the standard st-image-weston image following this guide:
https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_Package
After starting the build with
bitbake st-image-weston
When it reaches around the 68% of the process I get the following error:
ERROR: tf-a-stm32mp-2.2.r1-r0 do_compile: oe_runmake failed
ERROR: tf-a-stm32mp-2.2.r1-r0 do_compile: Execution of '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/temp/run.do_compile.21431' failed with exit code 1:
make: Entering directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
WARNING: exit code 1 from a shell command.
ERROR: Logfile of failure stored in: /home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/temp/log.do_compile.21431
Log data follows:
| DEBUG: Executing python function tfaconfig_env
| DEBUG: Python function tfaconfig_env finished
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 CROSS_COMPILE=arm-ostl-linux-gnueabi- DEBUG=1 LOG_LEVEL=40 PLAT=stm32mp1 ARCH=aarch32 ARM_ARCH_MAJOR=7 STM32MP_SDMMC=1 STM32MP_EMMC=1 STM32MP_SPI_NOR=1 STM32MP_RAW_NAND=1 STM32MP_SPI_NAND=1 -C /home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/git DTB_FILE_NAME=stm32mp157a-dk1.dtb BUILD_PLAT=/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/build/trusted AARCH32_SP=sp_min
| ERROR: oe_runmake failed
| make: Entering directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
| make: *** No targets specified and no makefile found. Stop.
| make: Leaving directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
| WARNING: exit code 1 from a shell command.
| ERROR: Execution of '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work/stm32mp1-ostl-linux-gnueabi/tf-a-stm32mp/2.2.r1-r0/temp/run.do_compile.21431' failed with exit code 1:
| make: Entering directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
| make: *** No targets specified and no makefile found. Stop.
| make: Leaving directory '/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/build-openstlinuxweston-stm32mp1/tmp-glibc/work-shared/stm32mp1/tfa-source'
| WARNING: exit code 1 from a shell command.
|
ERROR: Task (/home/osboxes/openstlinux-5.4-dunfell-mp1-20-06-24/layers/meta-st/meta-st-stm32mp/recipes-bsp/trusted-firmware-a/tf-a-stm32mp_2.2.bb:do_compile) failed with exit code '1'
I haven't added anything besides the cloned repository.
Am I doing something wrong?
Solved! Go to Solution.
2020-07-21 12:49 AM
Thank you @Community member it worked!
It seems a bit strange to me since I already tried to clean the whole st-image-weston recipe and it didn't work. Is there a difference between cleaning everything or the single recipe?
Thanks again and have a good day.
2020-07-21 02:33 AM
Actually "-c cleanall st-image-weston" does not manage dependences as you may expect. So there is no global clean command for an image.
To start from scratch when you suspect corrupted environment it's recommended to destroy tmp-glibc and sstate-cache folders.
Olivier
2020-08-13 04:17 AM
I had exactly the same problem on an Ubuntu 20.04 machine and the DISTRO=openstlinux-weston MACHINE=stm32mp1 configuration.
Your proposed solution worked here too. Thanks!
2020-10-22 08:30 AM
Yes, the bitbake -c cleanall tf-a-stm32mp works (as a workaround). Any idea on how to implement a proper fix for this issue?