On 1/11/23 3:28 PM, Chris Laplante via lists.yoctoproject.org wrote:
Has anyone seen compilation failures like these with fsbl-firmware or pmu-
firmware? We generally see these failures after setting up new build systems
and making a build for the first time.
DEBUG: Executing shell function do_compile
/home/user/yocto/build/tmp/work/digilent_genesys_zu-poky-linux/fsbl-
firmware/2022.1+gitAUTOINC+56d94a506f-r0/temp/run.do_compile.22073:
line 153: cd: /home/user/yocto/build/tmp/work/digilent_genesys_zu-poky-
linux/fsbl-firmware/2022.1+gitAUTOINC+56d94a506f-r0/git/fsbl-
firmware/fsbl-firmware: No such file or directory
I dug a little more into this and I think the issue is that the fsbl-firmware
recipe (and pmu-firmware, among others) sets B like this:
B = "${S}/${XSCTH_PROJ}"
But xsctapp.bbclass has this in do_compile:
cd ${B}/${XSCTH_PROJ}
Most components can build in a separate build directory, but not all of them.
Thus the former uses ${S}.
The expansion gives:
cd ${S}/${XSCTH_PROJ}/${XSCTH_PROJ}
which explains the error.
I'm not really sure whether it's the recipe or the bbclass that is at fault
here, so I'd appreciate if someone else could take a look. It's also not clear
to me why BitBake sometimes seems to not expand ${B}.
Check 2022.2 and honister branches. I don't know why this would be any
different (behavior wise) then the other code. This is being used a ton by all
of the boards.
--Mark
Thanks,
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5126):
https://lists.yoctoproject.org/g/meta-xilinx/message/5126
Mute This Topic: https://lists.yoctoproject.org/mt/96202605/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
