[OE-core] BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing
Robert P. J. Day
rpjday at crashcourse.ca
Tue Jan 29 09:08:10 UTC 2013
not sure if this is expected behaviour, but i'm using the meta-ti
layer to build a core-image-minimal for a am180x-evm. i'm using
"own-mirrors" to use my own premirrors directory and i've collected
all of the necessary tarballs and actually completed the build, after
which i make sure i have saved all of the tarballs so i don't need
to download anything for a subsequent build.
as a test, i totally delete my build and start over, but this time
with
BB_NO_NETWORK = "1"
which i assumed would still work. instead, i almost immediately got
this:
$ bitbake -c fetch core-image-minimal
Pseudo is not present but is required, building this first before the
main build
ERROR: ExpansionError during parsing
/home/rpjday/oe/dist/layers/meta-ti/recipes-bsp/u-boot/u-boot_2013.01.bb:
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://arago-project.org/git/projects/u-boot-keystone.git
DEV.MCSDK-03.00.00.06 (for url None)
ERROR: Command execution failed: Exited with 1
that's not even the version of u-boot that's going to be used, as
"bitbake -s" shows:
u-boot :2009.11+r68+gitr5f16b8551b125f16cd8d58f278cb25b94272fd9f-r68
so i'm guessing that what's happening here is that even though the
u-boot recipe file u-boot_2013.01.bb will contribute nothing to this
build, its parsing alone requires network access, which makes the
usage of BB_NO_NETWORK = "1" somewhat useless in this context.
am i misreading something? thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
More information about the Openembedded-core
mailing list