From: Martin Jansa <martin.jansa@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing
Date: Tue, 29 Jan 2013 10:44:22 +0100 [thread overview]
Message-ID: <20130129094422.GJ16904@jama.palm1.palmone.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301290359260.12134@oneiric>
[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]
On Tue, Jan 29, 2013 at 04:08:10AM -0500, Robert P. J. Day wrote:
>
> 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
It's using tag instead of hash in SRCREV, so it behaves the same as
SRC_URI = "git://.*;tag=foo" and tries to access upstream repo to
convert tag name to hash (or check if it's still the same hash as when
you've built it last time.
Cheers,
> 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
> ========================================================================
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-01-29 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 9:08 BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing Robert P. J. Day
2013-01-29 9:44 ` Martin Jansa [this message]
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=20130129094422.GJ16904@jama.palm1.palmone.com \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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