Open elockman opened 1 year ago
Here is the log file from above. log.do_install.3808492
Hi @elockman, Does your system meet the minimum system requirements?
@Dharma-B, yes I am building on a desktop dedicated to builds. I needed to create the following bbappend file in order to get it to build. I'm not sure why, exactly. Does this point to a cmake issue?
do_install:prepend:sama5d2() {
install -Dm 644 ${S}/app/pkcs11/slot.conf.tmpl ${D}${localstatedir}/lib/cryptoauthlib/slot.conf.tmpl
}
FILES:${PN} += "${sysconfdir}/cryptoauthlib "
Hi @elockman, We didn't encounter such an issue, to reproduce the same could you please share the snapshot of bitbake build configurations?
@elockman,
I saw this a couple of days ago. I had installed cryptoauthlib on the host PC while working with my meta layer which the only change I can think of that happened. I manually removed the install, removed the tmp dir and rebooted the machine. Then my build worked.
I think all of that is anecdotal as I don't see how having CAL installed on the host PC would cause any issues.
I manually removed the build and started over, but it didn't resolve the issue. I didn't reboot. I can try that again.
On Thu, Sep 14, 2023, 7:22 AM Matt Wood @.***> wrote:
@elockman https://github.com/elockman,
I saw this a couple of days ago. I had installed cryptoauthlib on the host PC while working with my meta layer which the only change I can think of that happened. I manually removed the install, removed the tmp dir and rebooted the machine. Then my build worked.
I think all of that is anecdotal as I don't see how having CAL installed on the host PC would cause any issues.
— Reply to this email directly, view it on GitHub https://github.com/linux4sam/meta-atmel/issues/261#issuecomment-1719442306, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACD7UX57LTIH54K6YSE4EY3X2MAHRANCNFSM6AAAAAA4VGUKPY . You are receiving this because you were mentioned.Message ID: @.***>
I am seeing the same issue. I even built in a new folder. These are the commands I run in the newly created folder:
git clone https://git.yoctoproject.org/poky && cd poky && git checkout -b kirkstone yocto-4.0.9 && cd -
git clone git://git.openembedded.org/meta-openembedded && cd meta-openembedded && git checkout -b kirkstone df452d && cd -
git clone https://github.com/linux4sam/meta-atmel.git -b kirkstone
git clone https://git.yoctoproject.org/meta-arm && cd meta-arm && git checkout -b kirkstone yocto-4.0.1 && cd -
cd poky
mkdir build-microchip
export TEMPLATECONF=${TEMPLATECONF:-../meta-atmel/conf}
source oe-init-build-env build-microchip
MACHINE=sama5d27-som1-ek-sd bitbake microchip-headless-image
This does not have any of my code. It should be a vanilla build.
I have a solution with the bbappend file shared above, so this is no longer blocking for me. Just looking to see if this helps others.
I am able to build the core image with:
MACHINE=sama5d27-som1-ek-sd bitbake core-image-minimal
But I run into a cryptoauthlib error when I run:
MACHINE=sama5d27-som1-ek-sd bitbake microchip-headless-image
I get the following error:I also see:
The image builds if I comment out the image recipe line 20:
IMAGE_INSTALL:append:sama5d2 = " cryptoauthlib python3-cryptoauthlib p11-kit"
or if I change it to:IMAGE_INSTALL:append:sama5d2 = " python3-cryptoauthlib p11-kit"
Any thoughts @Dharma-B? Is anyone else seeing this?