Am 02.10.2012 um 23:22 schrieb Martin Jansa <martin.ja...@gmail.com>:
> On Tue, Oct 02, 2012 at 05:17:23PM -0400, Evade Flow wrote: >> I'm trying to build core-image-sato for my Pandaboard ES, following the >> instructions posted here: >> >> - http://maniacbug.wordpress.com/2012/08/03/pandayocto/ >> >> Thus, my OE build configuration looks like this: >> >>> OE Build Configuration: >>> BB_VERSION = "1.15.2" >>> TARGET_ARCH = "arm" >>> TARGET_OS = "linux-gnueabi" >>> MACHINE = "pandaboard" >>> DISTRO = "poky" >>> DISTRO_VERSION = "1.2.1" >>> TUNE_FEATURES = "armv7a vfp neon cortexa9" >>> TARGET_FPU = "vfp-neon" >>> meta >>> meta-yocto = "denzil:65ffa7395055f7e012cb973f63f92380828eed0d" >>> meta-ti = "(nobranch):30fb40ebc13614a74c2e237927c60ac43e01d1bc" >> >> I have these lines in my .gitconfig: >> >>> [http] >>> proxy=http://user:pas...@usaprox.lightning.com:8080 >> >> so I'd expect URLs like this one (from the meta-ti layer's >> linux-omap4_3.1.0.bb recipe) to work fine: >> >>> SRC_URI = >>> "http://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git;protocol=git;branch=ti-ubuntu-3.1-1282 >>> \ > > This url seems wrong, it should start with git:// if you want to clone > git repo. > > Because it starts with http:// normal fetch (like wget) was used so it > downloaded probably some http code (see that kernel-ubuntu.git file) > instead of any relevant source. I ran into the same issue a few days ago. It seems yocto only supports git fetch through servers providing the repositories through the git protocol. A way to use git repositories which are provided through http or https would be quite a good thing to have. -Julian > >>> >>> file://0001-Makefile.fwinst-fix-install-breakage-for-FW-images-r.patch \ >>> file://defconfig \ >>> " >> >> From what I can tell, though, bitbake isn't handling this SRC_URI >> correctly, and I get: >> >>> ERROR: Command Error: exit status: 1 Output: >>> Applying patch >>> 0001-Makefile.fwinst-fix-install-breakage-for-FW-images-r.patch >>> patching file scripts/Makefile.fwinst >>> Hunk #1 FAILED at 27. >>> 1 out of 1 hunk FAILED -- rejects in file scripts/Makefile.fwinst >>> Patch 0001-Makefile.fwinst-fix-install-breakage-for-FW-images-r.patch does >>> not apply (enforce with -f) >>> ERROR: Function failed: patch_do_patch >> >> If I examine the folder: >> >> build/tmp/work/pandaboard-poky-linux-gnueabi/linux-omap4-3.1.0-r0 >> >> I see that it contains no source code. It does, however, contain a file >> named 'kernel-ubuntu.git', whose content is exactly the same as you'd >> get if you typed: >> >> wget http://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git >> >> This seems like a bug, possibly related to one of these: >> >> - http://bugzilla.yoctoproject.org/show_bug.cgi?id=3119 >> - http://bugzilla.yoctoproject.org/show_bug.cgi?id=3175 >> >> >> Maybe this has been fixed since denzil, but... everything I read about >> the current state of support for the Pandaboard suggests sticking with >> denzil/gcc 4.6. Is there some workaround I can use to get past this >> error? Also, assuming these instructions worked for the author of the >> original blog post, I wonder what the difference is with my setup. >> >> Here are my mods to conf/local.conf, in case it's helpful: >> >>> MACHINE = "pandaboard" >>> BBMASK = "meta-ti/recipes-misc" >>> PACKAGE_CLASSES = "package_ipk" >>> CONNECTIVITY_CHECK_URIS="" >>> BB_GENERATE_MIRROR_TARBALLS = "1" >>> SOURCE_MIRROR_URL ?= "file:///home/evadeflow/projects/poky-mirror/" >>> INHERIT += "own-mirrors" >> >> And this is my bblayers.conf: >> >>> # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf >>> # changes incompatibly >>> LCONF_VERSION = "4" >>> >>> BBFILES ?= "" >>> BBLAYERS ?= " \ >>> /home/evadeflow/projects/poky-git/meta \ >>> /home/evadeflow/projects/poky-git/meta-yocto \ >>> /home/evadeflow/projects/poky-git/meta-ti \ >>> " >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > -- > Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto