• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 2868 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Yocto/bitbake (MCSDK) build without network

Lance Jump
Expert 1280 points

I am using MCSDK 3.0.3.15 and the build is broken because git.ti.com is down for most of the day. The failure due to network issues has happened several times in the past because of sites being down, packages being removed from sites, or my network being down or our proxy being down, whatever.

I tried to build without the network (BB_NO_NETWORK = "1") and have not been successful. I have downloaded and made proper tarballs of everything I need, but it seems that some (many) of the recipes are expressed in forms that required contacting the server even with the data locally available at my SOURCE_MIRROR_URL.

Are there any plans to "fix" this so that a non-network build is possible? Is this even considered something to be "fixed" or the inability to build without the network the planned situation?

Thanks,

Lance

  • 0
    TI__Guru* 81335 points

    Lance,

    We have not received such issues from customer. Thank you for posting. 

    Could you please provide the  breaking links or build log to look in to the issue? 

    Yes. It is possible to build without the network however it would be difficult to match the file name and the checksum check available in BB recipes.

    Also we would suggest you to use latest MCSDK for development.

    Thank you.

  • 0 in reply to Raja
    Expert 1280 points

    Rajasekaran,

    I cannot provide all the failing recipes because the build stops when it encounters one. A few weeks back, I tried pursuing this by fixing each recipe and re-running, but I gave up.

    I just now ran it with BB_NO_NETWORK and failed immediately as it processed:

    meta-arago/meta-arago-extras/recipes-connectivity/hostap/hostap-daemon_r5.sp4.01.bb

    The failure message was:

    "ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception NetworkAccess: Network access disabled through BB_NO_NETWORK but access requested with command git ls-remote git://github.com/TI-OpenLink/hostap.git ol_R5.SP4.01 (for url None)"

    The problem is the following line in the recipe:

    SRCREV = "ol_R5.SP4.01"

    Replacing it with:

    SRCREV = "24422aac51de27e9441b8084616b2cfc01e3b81d"

    fixes it. (That number can be obtained via "git ls-remote" from the git server, or locally from the archived tarball for that repository.)

    But then another recipe fails for similar reasons:

    meta-arago/meta-arago-extras/recipes-connectivity/hostap/hostap-daemon_r5.00.18.bb

    And so on. I spent a couple of hours doing this and just gave up. A grep of the MCSDK bitbake sources shows that this SRCREV construction is in lots of places.

    You said "Yes. It is possible to build without the network however it would be difficult to match the file name and the checksum check available in BB recipes." I'm not sure what you mean by that. The file/checksum matching should be "automatic" if one follows the yocto/bitbake instructions for creating a local repository mirror. Basically, you run it with the network once and let it get everything and package it into tarballs. Then you should be able to run without the network.

    You also said "We have not received such issues from customer." Do you mean broken builds because of sites being down and such. I know customers have reported these issues because the first time it happened to me, I searched the forums and found such reports.

    If you mean that customers have not reported issues building with no network, do you know of anyone who has successfully built that way? Maybe no one else has tried.

    As I said in an earlier post, we are not prepared to switch MCSDK versions just yet. However, I did create a VM with the latest MCSDK (3.1.1.4) and got similar failures.

    Thanks,

    Lance