On Tue, Nov 20, 2012 at 12:34:47PM -0500, Robert P. J. Day wrote: > On Tue, 20 Nov 2012, Denys Dmytriyenko wrote: > > > On Tue, Nov 20, 2012 at 11:24:20AM -0500, Robert P. J. Day wrote: > > > > > > i'm sure there's a trivial workaround/explanation for this, but i > > > wanted to build the basic meta-ti based build for my panda ES, so i > > > started with oe-core and added the meta-ti layer. then, because of > > > some license issues (and based on a quick google search), i added this > > > to my local.conf: > > > > > > BBMASK = "meta-ti/recipes-misc" > > > > > > at that point, after selecting "pandaboard" as the machine, i wanted > > > to prefetch everything: > > > > > > $ bitbake -c fetchall core-image-minimal > > > > > > which used solely my pre-mirror directory so that didn't take long. > > > > > > *then*, because i allegedly had fetched everything i needed for the > > > build, i edited my site.conf file and added: > > > > > > BB_NO_NETWORK = "1" > > > > > > which, AIUI, should be perfectly safe since i had just done a > > > fetchall. not so: > > > > > > ERROR: Function failed: Network access disabled through BB_NO_NETWORK > > > but access requested with command git clone --bare --mirror > > > git://www.denx.de/git/u-boot.git > > > /home/rpjday/y/builds/ti/panda/downloads/git2/www.denx.de.git.u-boot.git > > > (for url None) > > > ERROR: Logfile of failure stored in: > > > /home/rpjday/y/builds/ti/panda/tmp-eglibc/work/pandaboard-oe-linux-gnueabi/u-boot-2011.12-r8/temp/log.do_fetch.29635 > > > > > > hmmmmmm ... > > > > > > $ bitbake -s | grep u-boot > > > nativesdk-u-boot-mkimage :2011.06-r0 > > > u-boot :2011.12-r8 > > > u-boot-fw-utils :2011.06-r1 > > > u-boot-mkimage :2011.06-r0 > > > u-boot-mkimage-native :2011.06-r0 > > > $ > > > > > > ok, now i'm confused. the above suggests that the version of u-boot > > > to be used here is 2011.12-r8, but that was never fetched, and it's > > > only now toward the end of the build that the fetch is attempted. > > > > > > can someone clarify what's happening here? why did my "fetchall" > > > operation not fetch everything the build was going to need? > > > > Is that because u-boot is not in a standard DEPENDS/RDEPENDS > > dependency tree, but rather in EXTRA_IMAGEDEPENDS list? I'm copying > > bitbake and oe-core lists, as I don't think it's meta-ti specific > > issue - u-boot recipe looks fine. > > good question ... for which i don't know the answer. to make sure > this is reproducible, i blew everything away and started from scratch > with a new panda build. here's my bblayers.conf: > > but when i do a "fetchall", i don't get u-boot_2011.12. only when i > try to build a core-image-minimal does the build fail toward the end > trying to fetch u-boot_2011.12. here's the layering info: > > i'm sure i'm just doing something silly, but i've never run into the > situation where a "fetchall" doesn't actually fetch absolutely > everything that's needed for the build.
Try adding CORE_IMAGE_EXTRA_INSTALL="u-boot" somewhere, like local.conf and if that fixes your usecase, it has to be a bug with bitbake forgetting to pre-fetch machine's specific EXTRA_IMAGEDEPENDS - file a bug then. -- Denys _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
