The branch and commit line up in my view. Did you experience a temporary github error? Or is your network being blocked/tampered with in some way?

https://github.com/xilinx/qemu/tree/xlnx_rel_v2022.1

That is a link directly to the branch, and the comment 52a9b22f is the head of that branch.


I'd suggest doing a bitbake qemu-xilinx-native -c cleanall, followed by a bitbake qemu-xilinx-native -c do_fetch and see if it works.


QEMU does use submodules, it's possible one of the referred to submodules is no longer available at the linked reference.

See:

https://github.com/Xilinx/qemu/blob/xlnx_rel_v2022.1/.gitmodules

I did spot check some of them and they appeared to be there. Most of the modules are gitlab, did you experience an outage there that has been resolved?

--Mark

On 2/22/23 9:07 AM, Karumuri, Vivith via lists.yoctoproject.org wrote:
Hello,

I am trying to build a minimal image for Xilinx ZCU102 board using latest version of Yocto Poky (honister) using meta-xilinx BSP layer (honister).

Build fails for a do_fetch task in the recipe "meta-xilinx/meta-xilinx-core/recipes-devtools/qemu/qemu-xilinx-native_2022.1.bb <https://1.bb>". Attached is my build output and qemu-xilinx.inc recipe.

This recipe tries to download from

  * HOMEPAGE: "https://github.com/xilinx/qemu/ 
<https://github.com/xilinx/qemu/>"
  * XILINX_QEMU_VERSION ?= "v6.1.0"
  * BRANCH ?= "xlnx_rel_v2022.1"
  * SRCREV = "52a9b22faeb149a6b17646b1f912f06ea6c269ca"

I checked manually in that homepage and this referenced branch does not exist??

Please provide a latest recipe for fixing this issue.

Thank you very much.

Regards,
Vivith Karumuri


-Bruker Confidential-





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5163): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5163
Mute This Topic: https://lists.yoctoproject.org/mt/97165749/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to