i.MX Yocto build fails with fetch error from dpdk-20.11

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.MX Yocto build fails with fetch error from dpdk-20.11

802 Views
Show
Contributor I

I am trying to build i.MX Yocto with imx-5.10.72-2.2.0.xml and it fails when trying to fetch the dpdk-20.11.

On the other hand, when I tried to build i.MX Yocto with imx-5.10.52-2.1.0.xml, it could fetch dpdk-20.11. Thus, I checked recipe diffs about meta-imx/meta-sdk/recipes-extended/dpdk/dpdk.inc between 5.10.52 and 5.10.72. 5.10.72's recipe assigned the branch as "SRCBRANCH = "20.11-qoriq"", also it changed revision to "ffc08d9998c962d5716ae3a63044ab08d9f51d86". In 5.10.52's recipe doesn't assign the branch, and its revision is "259400ae8798aecbf7392cd61010a7b1242bd833". In addition, I couldn't find the branch "20.11-qoriq" in  "git://source.codeaurora.org/external/qoriq/qoriq-components/dpd" and the revision "ffc08d9998c962d5716ae3a63044ab08d9f51d86". imx-5.10.72-2.2.0.xml's dpdk recipe seems wrong in branch/revision value.

ERROR: dpdk-20.11-r0 do_fetch: Fetcher failure: Unable to find revision ff07b5044cb4b22e8bc5003966d99f27396b0d00 in branch 20.11-qoriq even from upstream
ERROR: dpdk-20.11-r0 do_fetch: Fetcher failure for URL: 'git://source.codeaurora.org/external/qoriq/qoriq-components/dpdk;protocol=https;branch=20.11-qoriq'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/show/latest_imx/bld-xwayland/tmp/work/cortexa53-crypto-poky-linux/dpdk/20.11-r0/temp/log.do_fetch.635407
ERROR: Task (/home/show/latest_imx/sources/meta-imx/meta-sdk/recipes-extended/dpdk/dpdk_20.11.bb:do_fetch) failed with exit code '1'

0 Kudos
Reply
2 Replies

796 Views
joanxie
NXP TechSupport
NXP TechSupport

I have built it successfully, it seems the network issue, try to delete this package and build again

 

0 Kudos
Reply

776 Views
Show
Contributor I

I tried 2 times for building. Actually, it worked well at yesterday, but it didn't work at last Monday. Yesterday, I did resync by repo, however, I haven't checked new changesets. So, I'm not sure this result by the something new changeset effect or not. In my opinion, I think this could be closed right now. If I have something issue, let me reopen or create new topic.

0 Kudos
Reply