Re: [Angstrom-devel] Current Angstrom build for BeagleBone - 3.8 kernel fetch fails
Op 5 mei 2014, om 00:04 heeft Bob Feretich bob.feret...@rafresearch.com het volgende geschreven: On 5/4/2014 7:09 AM, Koen Kooi wrote: Op 4 mei 2014, om 11:07 heeft Bob Feretich bob.feret...@rafresearch.com het volgende geschreven: I am trying to build the Angstrom system that ships with the BeagleBone Black from source. bitbake cloud9-gnome-image ... ERROR: Function failed: Fetcher failure for URL: 'git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y'. Unable to fetch URL from any source. It uses the EOLed 3.8 kernel, which seems to be no longer available at kernel.org. It's still available: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.8.y maybe kernel.org had a small hickup in their server? When I bitbake, the do_fetch starts for the kernel... there is very little network traffic, then the fetch times out. After repeating this several times over a couple days (thinking that kernel.org had a server problem) and receiving your response that the kernel EOLed 3.8 kernel was still available, I manually did the kernel git. I can manually git clone or git fetch the kernel successfully. bitbake -c cleanall virtual/kernel ...does not fix the condition. Attempts to fetch the kernel via bitbake still fail. The problems seems to be the state that OE has the current build is in. Is there a way to reset this condition without starting he whole build over? In the sources/downloads dir remove the dirs with 'kernel.org' in them in the git2/ subdir (sources/downloads/git2/*kernel.org*). regards, Koen Regards, Bob However, this kernel seems to be supported at... https://github.com/beagleboard/kernel/ Is this the right place from which to fetch the kernel? If so, which patches should I use, the ones provided with the linux-mainline_3.8.bb recipe or the ones at github.com? Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] OE Changelog since 2014-04-27 until 2014-05-04
Changelog since 2014-04-27 until 2014-05-04. Projects included in this report: bitbake: git://git.openembedded.org/bitbake openembedded-core: git://git.openembedded.org/openembedded-core meta-openembedded: git://git.openembedded.org/meta-openembedded meta-angstrom: git://github.com/Angstrom-distribution/meta-angstrom.git meta-arago: git://arago-project.org/git/meta-arago.git meta-beagleboard: git://github.com/beagleboard/meta-beagleboard.git meta-browser: git://github.com/OSSystems/meta-browser.git meta-bug: git://github.com/buglabs/meta-bug.git meta-chicken: git://github.com/OSSystems/meta-chicken meta-efikamx: git://github.com/kraj/meta-efikamx.git meta-ettus: http://github.com/koenkooi/meta-ettus.git meta-fsl-arm: git://git.yoctoproject.org/meta-fsl-arm meta-fsl-arm-extra: git://github.com/Freescale/meta-fsl-arm-extra.git meta-fsl-ppc: git://git.yoctoproject.org/meta-fsl-ppc meta-guacamayo: git://github.com/Guacamayo/meta-guacamayo.git meta-gumstix: git://github.com/gumstix/meta-gumstix.git meta-gumstix-community: git://gitorious.org/schnitzeltony-oe-meta/meta-gumstix-community.git meta-handheld: git://git.openembedded.org/meta-handheld meta-igep: http://github.com/ebutera/meta-igep.git meta-intel: git://git.yoctoproject.org/meta-intel meta-ivi: git://git.yoctoproject.org/meta-ivi meta-java: git://github.com/woglinde/meta-java meta-kde: git://gitorious.org/openembedded-core-layers/meta-kde.git meta-micro: git://git.openembedded.org/meta-micro meta-mono: git://git.yoctoproject.org/meta-mono.git meta-netbookpro: git://github.com/tworaz/meta-netbookpro meta-nslu2: git://github.com/kraj/meta-nslu2 meta-opie: git://git.openembedded.org/meta-opie meta-qt3: git://git.yoctoproject.org/meta-qt3 meta-qt5: git://github.com/meta-qt5/meta-qt5.git meta-slugos: git://github.com/kraj/meta-slugos meta-systemd: git://git.yoctoproject.org/meta-systemd meta-raspberrypi: git://github.com/djwillis/meta-raspberrypi.git meta-smartphone: http://git.shr-project.org/repo/meta-smartphone.git meta-ti: git://git.yoctoproject.org/meta-ti meta-webos: git://github.com/openwebos/meta-webos.git meta-xilinx: git://git.yoctoproject.org/meta-xilinx meta-yocto: git://git.yoctoproject.org/meta-yocto openembedded: git://git.openembedded.org/openembedded Changelog for bitbake: Christopher Larson (1): codeparser: don't interact with the cache for subshells Jacob Kroon (1): fetch2: Cleanup file checksum generation, v2 Otavio Salvador (1): bb.utils, bb.codeparser: Add bb.utils.contains_any Richard Purdie (5): Revert fetch2: Cleanup file checksum generation bitbake: Bump version to 1.23.1 codeparser: Fix to better catch all getVar references persist_data: Avoid fsync() calls prserv/db: Avoid fsync() calls Volker Vogelhuber (1): HG Fetch with username and password in url Changelog for openembedded-core: Cristian Iorga (7): telepathy-glib: upgrade to 0.24.0 gstreamer1.0: upgrade to 1.2.4 gstreamer1.0-libav: upgrade to 1.2.4 gstreamer1.0-plugins-base: upgrade to 1.2.4 gstreamer1.0-plugins-good: upgrade to 1.2.4 gstreamer1.0-plugins-bad: upgrade to 1.2.4 gstreamer1.0-plugins-ugly: upgrade to 1.2.4 Drew Moseley (1): systemd: Check for HAVE_POSIX_FALLOCATE Irina Patru (1): distrodata.bbclass: Fix checkpkg functionality Jacob Kroon (2): sstate-cache-management: Minor cleanup of help text feature-arm-thumb.inc: Suppress false warning Laurentiu Palcu (12): xf86-input-synaptics: upgrade to 1.7.4 libdrm: upgrade to 2.4.53 xserver-xorg: upgrade to 1.15.1 python-pygobject: upgrade to 2.28.3 gdb: upgrade to 7.7 xproto: upgrade to 7.0.26 xrandr: upgrade to 1.4.2 xtrans: upgrade to 1.3.4 kexec-tools: upgrade to 2.0.6 nasm: upgrade to 2.11.02 xauth: upgrade to 1.0.9 fontconfig: upgrade to 2.11.1 Martin Jansa (4): feature-arm-thumb.inc: Replace inner quotes with apostrophes feature-arm-thumb.inc, arch-armv4.inc: Add arm to TUNE_FEATURES tune-cortexr4.inc: Add thumb and arm to TUNE_FEATURES feature-arm-thumb.inc: set ARMPKGSFX_THUMB only when thumb is in TUNE_FEATUR Max Eliaser (1): Add texinfo.bbclass; recipes that use texinfo utils at build-time inherit it Maxin B. John (2): openssl: enable ptest support ltp: update version to 20140422 Otavio Salvador (2): alsa-tools: Enable GTK support for X11, Wayland and DirectFB sanity: Bump BitBake minimal version to 1.23.0 Paul Barker (1): PR bumps to remove PRINC usage from meta-raspberrypi Paul Eggleton (6): sqlite3: restore upstream version numbering oeqa/controllers/masterimage: more robust master image startup classes/testimage: if start fails, don't try to stop scripts/contrib/serdevtry: add script to handle transient serial terminals scripts/contrib/dialog-power-control: add a trivial power prompt script oeqa: add proper handling for command errors where needed Richard Purdie (17): cross: Drop
[Angstrom-devel] Definition of Angstrom tasks
Is there a document that provides a detailed definition of what each these tasks do? Yocto, OE, and bitbake manuals tell us how to command a specific task to be run, but not what they do. The task name provides a good hint sometimes, but often that is not enough. Users shouldn't have to read the python code for this information. These descriptions should be a part of the yocto manual. Sections 5.3.4 to 5.3.11 of the Yocto mega-manual provide a good overview of some of these tasks in the context of a workflow, but doesn't mention most of these tasks and doesn't go into enough detail on the tasks it discusses. It wouldn't be appropriate to add more detail at that point in the manual, but it would be appropriate to include details regarding all of the tasks in an appendix. Examples... The manual states that do_fetch fetches source, but doesn't state that when git is used whether it performs a pull, fetch, or clone. What are the common failure conditions of do_fetch? And what should the user do to fix the problem? do_build is mentioned a few times, but there is no reference to it being the default task or what tasks are invoked by do_build and which are omitted. do_rm_work and do_wm_work_all are not mentioned at all. Result of listtasks: do_fetchall do_build do_devshell do_package_write_ipk do_cleansstate do_savedefconfig do_uboot_mkimage do_sizecheck do_strip do_packagedata_setscene do_configure do_clean do_deploy_setscene do_cleanall do_populate_lic do_populate_sysroot do_devicetree_image do_deploy do_menuconfig do_patch do_bundle_initramfs do_packagedata do_listtasks do_compile do_package_setscene do_populate_lic_setscene do_fetch do_checkuri do_compile_kernelmodules do_package_write_ipk_setscene do_package_write do_rm_work do_package do_unpack do_install do_checkuriall do_populate_sysroot_setscene do_rm_work_all I don't have the knowledge to create such an appendix, but I volunteer to be a proofreader. Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Definition of Angstrom tasks
On 05/05/2014 03:05 PM, Bob Feretich wrote: Is there a document that provides a detailed definition of what each these tasks do? Yocto, OE, and bitbake manuals tell us how to command a specific task to be run, but not what they do. I'd send this to yo...@yoctoproject.org since it is a general interest question. Philip The task name provides a good hint sometimes, but often that is not enough. Users shouldn't have to read the python code for this information. These descriptions should be a part of the yocto manual. Sections 5.3.4 to 5.3.11 of the Yocto mega-manual provide a good overview of some of these tasks in the context of a workflow, but doesn't mention most of these tasks and doesn't go into enough detail on the tasks it discusses. It wouldn't be appropriate to add more detail at that point in the manual, but it would be appropriate to include details regarding all of the tasks in an appendix. Examples... The manual states that do_fetch fetches source, but doesn't state that when git is used whether it performs a pull, fetch, or clone. What are the common failure conditions of do_fetch? And what should the user do to fix the problem? do_build is mentioned a few times, but there is no reference to it being the default task or what tasks are invoked by do_build and which are omitted. do_rm_work and do_wm_work_all are not mentioned at all. Result of listtasks: do_fetchall do_build do_devshell do_package_write_ipk do_cleansstate do_savedefconfig do_uboot_mkimage do_sizecheck do_strip do_packagedata_setscene do_configure do_clean do_deploy_setscene do_cleanall do_populate_lic do_populate_sysroot do_devicetree_image do_deploy do_menuconfig do_patch do_bundle_initramfs do_packagedata do_listtasks do_compile do_package_setscene do_populate_lic_setscene do_fetch do_checkuri do_compile_kernelmodules do_package_write_ipk_setscene do_package_write do_rm_work do_package do_unpack do_install do_checkuriall do_populate_sysroot_setscene do_rm_work_all I don't have the knowledge to create such an appendix, but I volunteer to be a proofreader. Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
