From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing
Date: Tue, 29 Jan 2013 04:08:10 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1301290359260.12134@oneiric> (raw)
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
========================================================================
next reply other threads:[~2013-01-29 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:08 Robert P. J. Day [this message]
2013-01-29 9:44 ` BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing Martin Jansa
2013-01-29 9:54 ` Robert P. J. Day
2013-01-29 11:24 ` Martin Jansa
2013-01-30 20:27 ` Robert P. J. Day
2013-01-30 20:34 ` Chris Larson
2013-01-30 20:34 ` Chris Larson
2013-01-30 20:49 ` Harvey Chapman
2013-01-30 20:53 ` Robert P. J. Day
2013-01-30 20:57 ` Chris Larson
2013-01-30 20:37 ` Robert P. J. Day
2013-01-30 20:44 ` Chris Larson
2013-01-30 21:31 ` Robert P. J. Day
2013-01-30 21:03 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1301290359260.12134@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox