Yocto Dunfell Recipe for Edge 1.4 #90
Conversation
ggjjj
force-pushed
the
ggjjj/support-for-1.4
branch
from
c89aadf to
4edf7df
Compare
|
I know it's still WIP, but if the meta-rust revision changes, please update it also in Readme. |
|
Hi, thanks for your work, would be awesome if we get this to work! I tried to build the feature branch (bitbake iotedge)and run into 2 issues: index 55712bd..987c7e5 100644
--- a/recipes-core/aziotctl/aziotctl_1.4.1.bb
+++ b/recipes-core/aziotctl/aziotctl_1.4.1.bb
@@ -239,8 +239,7 @@ SRC_URI += " \
"
LIC_FILES_CHKSUM=" \
-file://LICENSE;md5=0f7e3b1308cb5c00b372a6e78835732d \
-file://THIRDPARTYNOTICES;md5=11604c6170b98c376be25d0ca6989d9b \
+file://LICENSE;md5=4f9c2c296f77b3096b6c11a16fa7c66e \
"The second one seems to be more complicated: I am no rust expert. I am using an debian-based build container, libssl-dev is installed. I was able to build previous versions of meta-iotedge with the same container. Anybody an idea? |
|
Thanks for trying it out! @ggjjj is out for the next few days, but will resume upon returning. |
Yes will do. Once I finalize the version is finalized |
Thanks for trying it out. I had the same problem before my off. I suspect it to be openssl variable being unset and also the issue of missing the libtary "tssl2-sys". l am working on it and will update it here after resolution |
|
I remember being able to build something on the Rtone:dunfell branch (1.2.6 PR) patched to 1.4.0. (I wish I had more storage to go back and try to piece that back together...) |
|
same pesky error here: |
|
seems to be making it a bit farther ... now getting: | Running |
|
Please fix those license file checksums and remove pointers to missing THIRDPARTYNOTICES. It's pretty cumbersome to keep introducing local changes just to be able to build this... |
|
this project could use more love ;} |
|
@dvescovi1 Indeed, I'd assume there are some more Azure customers waiting for this not only the few of us here on Github |
|
I started a build and got this error: @rust-experts: Is this a local problem on my build machine or something wrong in the recipe? |
|
same error here too. |
were you able to overcome the libclang error? I have the same issue and got the meta-clang from https://github.com/kraj/meta-clang/blob/master/README.md @sindelar-fr |
fixed both. |
openssl issue should be fixed now |
we are doing our best to get this recipe asap. Appreciate your patience so far |
this is a known issue. meta-rust/meta-rust#343 I used the solution proposed to fix the issue by using the RUST_PANIC_STRATEGY set to "abort" |
updated the RUST version to 1.64 to overcome this issue along with the panic strategy mentioned previously |
|
Hi, still license issues: |
|
I was using the build.sh script to build in container.
I guess this has to do with the clang compiler. I can bitbake the clang package OK but not sure what else needs to be done. |
|
I added:
|
|
Just out of curiosity ... what platforms are you compiling it for? My TARGET_SYS is arm-poky-linux-gnueabi. |
initially qemux86-64 but eventually ARM64 but from what I understand that might also be an issue. |
Does not work for me...still complains about missing libclang on hardknott. |
|
|
I think you mean systemctl status aziot-tpmd ... not aziot-tmpd |
|
seems to be working now. I noticed I also had to do the same thing when IOT Edge set up the same way using official Debian 11 bullseye ARM64 RPI4 release w/TPM usings MS release packages. |
|
I added links I found helpful for migration in #95. Anything to add? |
|
Seems like an IoT Edge Runtime bug to me. |
@ggjjj @micahl @dvescovi1 Does this validate TPM path then? |
ggjjj
force-pushed
the
ggjjj/support-for-1.4
branch
from
b52d238 to
e949fbd
Compare
@dvescovi1 thank you for reporting your results! That sounds like an issue we recently fixed in edgeAgent. We're planning to merge these changes for the 1.4.2 as we know folks are waiting on it. We'll separately look to update the recipes for the most recent 1.4.3 that went out last week. We plan to use that as an opportunity to see what steps we'd need to take to automate the process further so that on future patch releases the recipe updates are easier. |
@maskimthedog yes, I believe so. |
I don't know off hand why the redeploy would be needed. Consider opening a github issue on the main iotedge repo for this as it doesn't sound specific to one OS or the other. |
* Add thud support (#19) * Initial thud support * Tweak the recipes and remove invalid items * Make layer thud only * Update README for Thud * Update source mirrors for thud * Update build branch to thud * Add master back * Remove source rev * Update to 1.0.8 (#25) * Update to 1.0.8 * Set libiothsm no build in iotedge-cli * Update to 1.0.9.4 for Thud (#40) * Update to 1.0.9.4 for Thud * Update third party notices md5sum * Pin meta-rust commit version * iotedge-cli RDEPENDS on libiothsm * Add build dependency on libiothsm * Update for dunfell (#43) * Update for dunfell * Use newer version of the rust compiler * RDEPENDS on docker not virtual/docker Remove unused recipes * Disable libgit2 for cargo Without this fix the build leads to an error : "invalid version 3 on git_proxy_options; class=Invalid (3)" * Update Dunfell branch to LTS (1.1.3) (#65) * Add 1.1.3 bitbake files. * Update sums for iotedge project file. * Fix daemon description. * Rmove extraneous comments. * TGZ package structure is a little different. Fix includes in the bitbake file. * Fix license path * Fix install paths. * More clearly mark generated section. * Update README.md (#66) Readme.md: Match the meta-rust layer revision from builds/checkin.yaml * We probably don't need to set CARGO_SRC_DIR (#68) * Update dunfell branch to 1.1.6 (#70) * Update dunfell branch to 1.1.6 * Update Dunfell branch to IoT Edge version 1.1.8 (#73) * Update Dunfell branch to IoT Edge version 1.1.8 * Use a newer container for Yocto builds. Make some script changes due to difference in the containers. * Update the MD5 hash for THIRDPARTYNOTICES. * changed git fetch from nobranch/AUTOREV to main branch (#79) * changed from nobranch/AUTOREV to main branch This fixes a recent bug introduced over the weekend which results in a bitbake expansion error. Specifically the error is the following, Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for github.com/Azure/hyperlocal-windows * nobranch/AUTOREV to main branch in iotedge-daemon This fixes a recent bug introduced over the weekend which results in a bitbake expansion error. Specifically the error is the following, Fetcher failure: Unable to resolve 'master' in upstream git repository in git ls-remote output for github.com/Azure/hyperlocal-windows * Update dunfell to 1.1.11 (#82) * Update dunfell to 1.1.11 * Update recipes to 1.1.15 (#85) Update the following recipe components to 1.1.15: - iotedge-cli - iotedge-daemon - libiothsm * Use 1ES agent for Checkin gate (#89) Previously the pipeline was run on the self-hosting pool, the ECSS team has mandate the self-hosting pools need to be retired in favor of the 1ES pools. This PR updates the checkin gate test agent to be running on 1ES VM instead of self-hosting VM. * Yocto Dunfell Recipe for Edge 1.4 (#90) * Draft Recipe for 1.4 IoT Edge * Add Panic strategy to unwind * Update receipes to 1.4.2 * TPM provsioning support and update dependencies * Update recipes to fix bug and Update documentation * Update README.md (#96) * Update Iotedge recipes to 1.4.4 * refactor * Update README.md * 1.4.4 changes * refactor * Update iotedge_1.4.4.bb Co-authored-by: Mike Yagley <[email protected]> Co-authored-by: David Robson <[email protected]> Co-authored-by: František Šindelář <[email protected]> Co-authored-by: donofan0 <[email protected]> Co-authored-by: yophilav <[email protected]> Co-authored-by: Micah Lewis <[email protected]>
|
@pierrickcurt, @maskimthedog, @Granjow, @sindelar-fr, @dvescovi1, @rschwarz-sotec, and @ElD4n1 let me know if there are errors in the credits: General availability: Yocto recipes for IoT Edge 1.4 LTS |
|
Thanks! I worked on it for Bühler, if you want to add a link. |
|
I worked on it for Mesh Systems.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Simon A. Eugster ***@***.***>
Sent: Wednesday, December 14, 2022 12:38:08 PM
To: Azure/meta-iotedge ***@***.***>
Cc: Rob Krakora ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/meta-iotedge] Yocto Dunfell Recipe for Edge 1.4 (PR #90)
Thanks! I worked on it for Bühler<https://www.buhlergroup.com/>, if you want to add a link.
—
Reply to this email directly, view it on GitHub<#90 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJZCEGKBGXN3U7JFJFZDRRTWNIAYBANCNFSM6AAAAAAQNVE6CU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
https://meshsystems.com/
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Rob Krakora ***@***.***>
Sent: Wednesday, December 14, 2022 12:39:50 PM
To: Azure/meta-iotedge ***@***.***>; Azure/meta-iotedge ***@***.***>
Cc: Mention ***@***.***>
Subject: Re: [Azure/meta-iotedge] Yocto Dunfell Recipe for Edge 1.4 (PR #90)
I worked on it for Mesh Systems.
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Simon A. Eugster ***@***.***>
Sent: Wednesday, December 14, 2022 12:38:08 PM
To: Azure/meta-iotedge ***@***.***>
Cc: Rob Krakora ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/meta-iotedge] Yocto Dunfell Recipe for Edge 1.4 (PR #90)
Thanks! I worked on it for Bühler<https://www.buhlergroup.com/>, if you want to add a link.
—
Reply to this email directly, view it on GitHub<#90 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AJZCEGKBGXN3U7JFJFZDRRTWNIAYBANCNFSM6AAAAAAQNVE6CU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ok, will try to get it updated before the editors for the Azure updates blog put a freeze on things before the holiday. |
|
Thanks! I worked on it for Y Soft if you want to link it too. |
Perfect, thanks for this credit ! |
|
Was able to squeeze in an update that should be live now. |
![https://ci6.googleusercontent.com/proxy/Sh-8YmBCXXgMOdOoPgPtgPnKQjxnBXcEwel_xmwS_cHPKRztClUPBPiJEHPdtG3Hei5hccBS7ONl-N_UCmjOHpHCwBzTomOq7BWdwmxz1KhrziiqbYJgeX4FOXOOh5DEqF8y=s0-d-e1-ft#http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/twitter_sig.png]<https://twitter.com/mesh_systems](https://ci6.googleusercontent.com/proxy/Sh-8YmBCXXgMOdOoPgPtgPnKQjxnBXcEwel_xmwS_cHPKRztClUPBPiJEHPdtG3Hei5hccBS7ONl-N_UCmjOHpHCwBzTomOq7BWdwmxz1KhrziiqbYJgeX4FOXOOh5DEqF8y=s0-d-e1-ft#http://cdn2.hubspot.net/hubfs/184235/dev_images/signature_app/twitter_sig.png]<https://twitter.com/mesh_systems){kind=link}
1.4 IoT Edge Yocto recipes with the update from the new architecture migration from 1.1