[yocto] Question about BB_NO_NETWORK
Gary Thomas
gary at mlbassoc.com
Fri Mar 27 10:09:40 PDT 2015
On 2015-03-27 11:00, Gary Thomas wrote:
> Can someone explain to me why this recipe (from meta-fsl-arm-extra)
> requires network access if I have a current (built today on a different
> machine) git tarball of the repository?
Oops, forgot the recipe:
>
> The error I get is:
>
> ERROR: Function failed: Network access disabled through BB_NO_NETWORK (or set indirectly due to use of BB_FETCH_PREMIRRORONLY) but access requested with command git -c
> core.fsyncobjectfiles=0 fetch -f --prune git://github.com/boundarydevices/u-boot-imx6.git refs/*:refs/* (for url
> git://github.com/boundarydevices/u-boot-imx6.git;branch=v2014.07-20140914)
> ERROR: Logfile of failure stored in:
> /local/imx6_2015-03-27/tmp/work/nitrogen6x-amltd-linux-gnueabi/u-boot-script-boundary/v2014.07+gitAUTOINC+fcb04d6103-r0/temp/log.do_fetch.22945
> Log data follows:
> | DEBUG: Executing python function do_fetch
> | DEBUG: Executing python function base_do_fetch
> | DEBUG: Trying Upstream
> | DEBUG: Running export
> PATH="/local/poky-cutting-edge/scripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin/arm-amltd-linux-gnueabi:/local/imx6_2015-03-27/tmp/sysroots/nitrogen6x/usr/bin/crossscripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/bin:/local/poky-cutting-edge/scripts:/local/poky-cutting-edge/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";
> export HOME="/home/gthomas"; git -c core.fsyncobjectfiles=0 branch --contains fcb04d6103e2a1f62d3ae197432559aee5621765 --list v2014.07-20140914 2> /dev/null | wc -l
> | DEBUG: Running export
> PATH="/local/poky-cutting-edge/scripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin/arm-amltd-linux-gnueabi:/local/imx6_2015-03-27/tmp/sysroots/nitrogen6x/usr/bin/crossscripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/bin:/local/poky-cutting-edge/scripts:/local/poky-cutting-edge/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";
> export HOME="/home/gthomas"; git -c core.fsyncobjectfiles=0 remote rm origin
> | DEBUG: Running export
> PATH="/local/poky-cutting-edge/scripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin/arm-amltd-linux-gnueabi:/local/imx6_2015-03-27/tmp/sysroots/nitrogen6x/usr/bin/crossscripts:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/usr/bin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/sbin:/local/imx6_2015-03-27/tmp/sysroots/i686-linux/bin:/local/poky-cutting-edge/scripts:/local/poky-cutting-edge/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games";
> export HOME="/home/gthomas"; git -c core.fsyncobjectfiles=0 remote add --mirror=fetch origin git://github.com/boundarydevices/u-boot-imx6.git
> | DEBUG: Python function base_do_fetch finished
> | DEBUG: Python function do_fetch finished
> | ERROR: Function failed: Network access disabled through BB_NO_NETWORK (or set indirectly due to use of BB_FETCH_PREMIRRORONLY) but access requested with command git -c
> core.fsyncobjectfiles=0 fetch -f --prune git://github.com/boundarydevices/u-boot-imx6.git refs/*:refs/* (for url
> git://github.com/boundarydevices/u-boot-imx6.git;branch=v2014.07-20140914)
> ERROR: Task 111 (/local/poky-cutting-edge/meta-fsl-arm-extra/recipes-bsp/u-boot/u-boot-script-boundary_git.bb, do_fetch) failed with exit code '1'
>
> The git tarball and full log are at http://www.mlbassoc.com/poky
>
> Is this a BUG? I'm using these layers:
> meta = "master:5c76cebc24675edb3dff473fce9b67cedff615db"
> meta-fsl-arm = "master:115aaced72fddc23024f8838f0eeb8ad5e37d048"
> meta-fsl-arm-extra = "master:22f6672c3ef58bf5070d0c6894a459fada66f55e"
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
-------------- next part --------------
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://Licenses/README;md5=025bf9f768cbcb1a165dbe1a110babfb"
DEPENDS = "u-boot-mkimage-native"
PV = "v2014.07+git${SRCPV}"
SRCREV = "fcb04d6103e2a1f62d3ae197432559aee5621765"
SRCBRANCH = "v2014.07-20140914"
SRC_URI = "git://github.com/boundarydevices/u-boot-imx6.git;branch=${SRCBRANCH}"
S = "${WORKDIR}/git"
inherit deploy
BOOTSCRIPT ?= "${S}/board/boundary/${MACHINE}/6x_bootscript-yocto.txt"
BOOTSCRIPT_imx6qsabrelite ?= "${S}/board/boundary/nitrogen6x/6x_bootscript-yocto.txt"
BOOTSCRIPT_nitrogen6x-lite ?= "${S}/board/boundary/nit6xlite/6x_bootscript-yocto.txt"
UPGRADESCRIPT = "${S}/board/boundary/nitrogen6x/6x_upgrade.txt"
do_mkimage () {
# allow deploy to use the ${MACHINE} name to simplify things
if [ ! -d board/boundary/${MACHINE} ]; then
mkdir board/boundary/${MACHINE}
fi
uboot-mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
-n "boot script" -d ${BOOTSCRIPT} \
board/boundary/${MACHINE}/6x_bootscript
uboot-mkimage -A arm -O linux -T script -C none -a 0 -e 0 \
-n "upgrade script" -d ${UPGRADESCRIPT} \
board/boundary/${MACHINE}/6x_upgrade
}
addtask mkimage after do_compile before do_install
do_deploy () {
install -d ${DEPLOYDIR}
install ${S}/board/boundary/${MACHINE}/6x_bootscript \
${DEPLOYDIR}/6x_bootscript-${MACHINE}-${PV}-${PR}
install ${S}/board/boundary/${MACHINE}/6x_upgrade \
${DEPLOYDIR}/6x_upgrade-${MACHINE}-${PV}-${PR}
cd ${DEPLOYDIR}
rm -f 6x_bootscript-${MACHINE} 6x_upgrade-${MACHINE}
ln -sf 6x_bootscript-${MACHINE}-${PV}-${PR} 6x_bootscript-${MACHINE}
ln -sf 6x_upgrade-${MACHINE}-${PV}-${PR} 6x_upgrade-${MACHINE}
}
addtask deploy after do_install before do_build
do_compile[noexec] = "1"
do_install[noexec] = "1"
do_populate_sysroot[noexec] = "1"
PACKAGE_ARCH = "${MACHINE_ARCH}"
COMPATIBLE_MACHINE = "(nitrogen6x|nitrogen6x-lite)"
More information about the yocto
mailing list