Hello community,
I am having a problem when configuring the SDK for P4080 and setting its built image (using bitbake fsl-image-X, with X being the type of image like full, core, minimal, etc.).
Whenever I use that command i get the following repeating message:
Delaying shutdown due to active processes which appear to be holding bitbake.lock:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
python 2721 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2722 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2724 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2725 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2726 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2727 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2728 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2729 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
python 2730 nxp 12u REG 8,2 0 3435820 /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/build_p4080ds/bitbake.lock
Without being able to avoid this situation and after exiting the terminal, the following error appears:
WARNING: Duplicate inclusion for /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-freescale-internal/conf/distro/imagedepends.conf in /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-freescale-internal/conf/layer.conf
WARNING: Duplicate inclusion for /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-freescale-internal/conf/distro/url-sha-references.conf in /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-freescale-internal/conf/layer.conf
WARNING: Duplicate inclusion for /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-virtualization/conf/distro/include/virt_security_flags.inc in /home/nxp/SDK/QorIQ-SDK-V1.9-20151210-yocto/sources/meta-virtualization/conf/layer.conf
We are stuck in this point and cannot continue with the image setting.
Any help would be kindly appreciated.
Thanks in advance,
Cheers,
Marc
已解决! 转到解答。
Hello Marc,
The bitbake.lock file is just used to ensure only one bitbake runs in a specific build folder at a time, as usual this file should be empty, probably your still doesn't use bitbake in a clean build environment.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Marc Morales,
If the build project wasn't created completely, the above error may occur.
Please go to the folder <install_path>/QorIQ-SDK-V1.9-20151210-yocto, remove "build_p4080ds" folder and execute the command "source ./fsl-setup-env -m p4080ds", please finish reading the EULA information and accept it, then you will enter into build_p4080ds folder automatically, please execute bitbake command.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Yiping,
Thank you for your quick answer. I am afraid, however, that is not the solution to my problem. I now understand what happens with bitbake and successfully deleted the "build_p4080ds" folder. After proceeding to execute the commands, though, it seems that when I try to build in an image (with the bitbake command from inside the build_p4080ds folder) the bitbake.lock error persists, informing me that it is held by some processes I already specified in my original message.
I do not understand what happens with bitbake.lock, as it is created exactly after I execute the command to create the image, and the processes that seem to be holding it are inside of it?
Thank you once more and have a great day as well.
Marc
Hello Marc,
The bitbake.lock file is just used to ensure only one bitbake runs in a specific build folder at a time, as usual this file should be empty, probably your still doesn't use bitbake in a clean build environment.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------