Re: [yocto] Yocto Eclipse Plugin
Hello Abhinav, On Mon, 2015-04-13 at 18:27 +, Bipnesh, Abhinav (Abhinav) wrote: > Hi All, > > I am trying to setup the Yocto Eclipse Plugin for Eclipse (Luna release). I > am able to install the Juno release plugin for 1.7.1 release. But while > configuring it I am facing issues as below > 1. When I try to provide BitBake directory as part of tool chain I get an > error that need to build meta-ide-support before configuring it. > As I did build meta-ide-support before setting up the path as I can see an > environment file present under /tmp path. You will need to provide the path to the build directory. This is the directory holding tmp. > 2. If I select Standard SDK option then it accepts the same i.e. it accept > environment file present under tmp directory as vaild which I suppose it > should not do. > 3. I already has Makefile based project which I am trying to configure in > eclipse by selecting Yocto as Toolchain. > But when I try to build it I am seeing its using platform GCC instead of > Yocto tool chain. Selecting the correct directory should set up the cross-compiler environment and fix this. > > How to fix the same as I cant change this project to an CMake based project. > > Is there as way I can use Kepler plugin instead of Juno as when I try the > same with Luna I am getting dependencies errors. You can find the plugin releases here: http://downloads.yoctoproject.org/releases/eclipse-plugin/ Cheers, Todor smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 1.7.1 ADT-installer errors
Hi, I'm new to Yocto (and embedded Linux for that matter). I was following the ADT manual to get started with application development. I tried using the ADT-installer script, but ran into some errors. Here's the relevant part of the installer log file: *Creating directory /home/spe/test-yocto/qemux86...Extracting rootfs: core-image-sato-sdk-qemux86.tar.bz2, using pseudo...tar (child): ./download_image/core-image-sato-sdk-qemux86.tar.bz2: Cannot open: No such file or directorytar (child): Error is not recoverable: exiting nowtar: Child returned status 2tar: Error is not recoverable: exiting now* There are no files in my /download_image directory so I guess they have not been properly retrieved from the repository. I looked at the repository for 1.7.1 at http://adtrepo.yoctoproject.org/1.7.1/rootfs/qemux86/ and some of the relevant files seem to be missing. Or did I mis a step somewhere? Sammy -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto Digest, Vol 53, Issue 97
Hi All, When I take kernel from the SVN I got the validation error that SRCREV is not proper. Could you please help me in resolving this issue. Thanks in advance. Regards, Raghavendra. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Saturday, February 21, 2015 4:04 AM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 53, Issue 97 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Simple recipe quit working in dizzy (akuster) -- Message: 1 Date: Fri, 20 Feb 2015 14:28:10 -0800 From: akuster To: yocto@yoctoproject.org Subject: Re: [yocto] Simple recipe quit working in dizzy Message-ID: <54e7b4fa@mvista.com> Content-Type: text/plain; charset=windows-1252; format=flowed On 02/20/2015 09:49 AM, Jim Rafert wrote: > Hi Paul, > > Thank you for taking an interest in this. > > I looked at the log.do_rootfs, and didn't see anything that was immediately > suspicious. > I have inlined the log at the end of my reply, here. > > I don't see how such a simple recipe could be broken by a Yocto bug, and not > have the > whole thing be massively broken. Is it possible for you to try your recipe on 'master'? that might tell use if something is missing in dizzy. - Armin > > -Jim- > > cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs > DEBUG: Executing python function rootfs_process_ignore > DEBUG: Python function rootfs_process_ignore finished > DEBUG: Executing python function rootfs_runtime_mapping > DEBUG: Python function rootfs_runtime_mapping finished > DEBUG: Executing python function do_rootfs > NOTE: configuring RPM platform settings > NOTE: configuring RPM system provides > NOTE: configuring RPM DB settings > NOTE: configuring Smart settings > NOTE: Note: adding Smart channel spectra_ls (35) > NOTE: Note: adding Smart channel i586 (30) > NOTE: Note: adding Smart channel all (25) > NOTE: adding Smart RPM DB channel > NOTE: Note: configuring RPM cross-install scriptlet_wrapper > NOTE: ## Generate rootfs ### > NOTE: Executing > '/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo > --update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ... > NOTE: Installing the following packages: libgcc1 parted grub dosfstools > psplash vim udev-extraconf rsyslog libsoci nss rpm unzip zip > spectra-postbuild smartpm e2fsprogs-tune2fs packagegroup-core-eclipse-debug > poco libstdc++6 sqlite3 e2fsprogs-e2fsck openssl-staticdev boost > packagegroup-core-ssh-openssh packagegroup-core-boot > packagegroup-core-full-cmdline rpmresolve ntp e2fsprogs-mke2fs util-linux > packagegroup-core-tools-debug openssl e2fsprogs sys-freedos > e2fsprogs-badblocks locale-base-en-us locale-base-en-gb > NOTE: to be installed: libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 > psplash@i586 vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 > rpm@i586 unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 > e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 > libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 > boost@i586 packagegroup-core-ssh-openssh@all > packagegroup-core-boot@spectra_ls packagegroup-core-full-cmdline@all > rpmresolve@i586 ntp@i586 e2fsprogs-mke2fs@i586 util-linux@i586 > packagegroup-core-tools-debug@all openssl@i586 e2fsprogs@i586 > sys-freedos@i586 e2fsprogs-badblocks@i586 locale-base-en-us@i586 > locale-base-en-gb@i586 > NOTE: > /home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/smart > --quiet > --data-dir=/home/jimr/tera/yocto/dizzy/build/tmp/work/spectra_ls-poky-linux/core-image-full-cmdline/1.0-r0/rootfs/var/lib/smart > install -y libgcc1@i586 parted@i586 grub@i586 dosfstools@i586 psplash@i586 > vim@i586 udev-extraconf@i586 rsyslog@i586 libsoci@i586 nss@i586 rpm@i586 > unzip@i586 zip@i586 spectra-postbuild@i586 smartpm@i586 > e2fsprogs-tune2fs@i586 packagegroup-core-eclipse-debug@all poco@i586 > libstdc++6@i586 sqlite3@i586 e2fsprogs-e2fsck@i586 openssl-staticdev@i586 > boost@i586 packagegroup-core-ssh-openssh@all > packagegroup-core-boot@spectra_ls packagegroup-core-full-cmdline@all > rpmresolve@i586 ntp@i586 e2fsprogs-mke2fs@i586 util-linux@i586 > packagegroup-core-tools-debug@all openssl@i586 e2fsprogs@i586 > sys-freedos@i586 e2fsprogs-badblocks@i586 locale-base-en-us@i586 > locale-base-en-gb@i586 > NOTE: Output from bash-4.3-r0@i586: > update-alternatives
[yocto] [Intel Edison] Changing kernel configuration results in "do_rootfs"-failure (Code 255)
I tried to add a module to the kernel configuration according to
http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html#changing-the-configuration
Here is what I have done:
File:
meta-mylayer/recipes-kernel/linux/linux-yocto_3.10.bbappend
Contains:
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI += "file://FTDI.cfg"
File:
meta-mylayer/recipes-kernel/linux/files/FTDI.cfg
Contains:
CONFIG_USB_SERIAL=y
CONFIG_USB_SERIAL_FTDI_SIO=y
File:
meta-mylayer/recipes-mylayer/images/mylayer-image.bb
Contains:
IMAGE_INSTALL += " \
linux-yocto \
[...]
Bitbake result:
ERROR: Unable to install packages. Command
'/home/ubuntu/development/edison-src/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl
-f
/home/ubuntu/development/edison-src/build/tmp/work/edison-poky-linux/geent-image/1.0-r0/opkg.conf
-o
/home/ubuntu/development/edison-src/build/tmp/work/edison-poky-linux/geent-image/1.0-r0/rootfs
--force_postinstall --prefer-arch-to-version install i2c-tools
run-postinsts nano useradd linux-yocto base-files postgresql
packagegroup-core-boot' returned 255:
[...]
Collected errors:
* opkg_install_cmd: Cannot install package linux-yocto.
[...]
ERROR: Function failed: do_rootfs
What might be wrong here?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] SRCREV Issue for custom linux kernel
Hi All, I got the an error while i am checking out the linux kernel from the SVN to build in the YOCTO project environment. Could please help me in resolving the Issue. Error log is: Log data follows: | DEBUG: Executing shell function do_validate_branches | NOTE: custom recipe is being built, forcing SRCREV to INVALID | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch | fatal: ambiguous argument 'INVALID': unknown revision or path not in the working tree. | Use '--' to separate paths from revisions | WARNING: exit code 128 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) Thanks in advance. Regards, Raghavendra K. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Tuesday, April 14, 2015 2:50 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 55, Issue 46 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) -- Message: 1 Date: Tue, 14 Apr 2015 09:20:38 + From: Raghavendra Kakarla To: "yocto@yoctoproject.org" Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 Message-ID: <1429003199394.19...@inedasystems.com> Content-Type: text/plain; charset="iso-8859-1" Hi All, When I take kernel from the SVN I got the validation error that SRCREV is not proper. Could you please help me in resolving this issue. Thanks in advance. Regards, Raghavendra. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Saturday, February 21, 2015 4:04 AM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 53, Issue 97 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Simple recipe quit working in dizzy (akuster) -- Message: 1 Date: Fri, 20 Feb 2015 14:28:10 -0800 From: akuster To: yocto@yoctoproject.org Subject: Re: [yocto] Simple recipe quit working in dizzy Message-ID: <54e7b4fa@mvista.com> Content-Type: text/plain; charset=windows-1252; format=flowed On 02/20/2015 09:49 AM, Jim Rafert wrote: > Hi Paul, > > Thank you for taking an interest in this. > > I looked at the log.do_rootfs, and didn't see anything that was immediately > suspicious. > I have inlined the log at the end of my reply, here. > > I don't see how such a simple recipe could be broken by a Yocto bug, and not > have the > whole thing be massively broken. Is it possible for you to try your recipe on 'master'? that might tell use if something is missing in dizzy. - Armin > > -Jim- > > cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs > DEBUG: Executing python function rootfs_process_ignore > DEBUG: Python function rootfs_process_ignore finished > DEBUG: Executing python function rootfs_runtime_mapping > DEBUG: Python function rootfs_runtime_mapping finished > DEBUG: Executing python function do_rootfs > NOTE: configuring RPM platform settings > NOTE: configuring RPM system provides > NOTE: configuring RPM DB settings > NOTE: configuring Smart settings > NOTE: Note: adding Smart channel spectra_ls (35) > NOTE: Note: adding Smart channel i586 (30) > NOTE: Note: adding Smart channel all (25) > NOTE: adding Smart RPM DB channel > NOTE: Note: configuring RPM cross-install scriptlet_wrapper > NOTE: ## Generate rootfs ### > NOTE: Executing > '/home/jimr/tera/yocto/dizzy/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo > --update -q /home/jimr/tera/yocto/dizzy/build/tmp/deploy/rpm/i586' ... > NOTE: Installing the following packages: libgcc1 parted grub dosfstools > psplash vim udev-extraconf rsyslog libsoci nss rpm unzip zip > spectra-postbuild smartpm e2fsprogs-tune2fs packagegroup-core-eclipse-debug > poco libstdc++6 sqlite3 e2fsprogs-e2fsck openssl-staticdev boost > packagegroup-core-ssh-openssh pac
Re: [yocto] Yocto Eclipse Plugin
Hello Abinhav, This is most likely caused by a mismatch between the plugin build (juno) and the IDE (luna). Please install the luna build of the plugin from here: https://autobuilder.yoctoproject.org/pub/nightly/CURRENT/eclipse-plugin/luna/org.yocto.sdk-development-201504140001-archive.zip Thanks, Todor On Tue, 2015-04-14 at 08:39 +, Bipnesh, Abhinav (Abhinav) wrote: > Hi, > > > > I was using the same URL as you suggested for the Yocto Eclipse > Plugin. Below is the snapshot of the error I am getting when I try to > configure it as Build System derived tool chain > > > > > > > > > > I already did build meta-ide-support and can see the > environment-setup-ppce5500-fsl-linux under /tmp. If I > select Standalone SDK the it starts work without any issue. > > > > > > Second issue I am facing is that when I import my existing project > which is a Makefile base I can see option for Yocto CMake Build > (Toolchain) as below > > > > > > > > So how to fix this as need to make it working with existing Makefile > based project. > > > > > > Any thoughts how to fix these issues. > > > > Thanks, > > Abhinav > > > > -Original Message- > From: Minchev, Todor [mailto:todor.minc...@intel.com] > Sent: Tuesday, April 14, 2015 12:38 > To: Bipnesh, Abhinav (Abhinav) > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Eclipse Plugin > > > > Hello Abhinav, > > > > On Mon, 2015-04-13 at 18:27 +, Bipnesh, Abhinav (Abhinav) wrote: > > > Hi All, > > > > > > I am trying to setup the Yocto Eclipse Plugin for Eclipse (Luna > release). I am able to install the Juno release plugin for 1.7.1 > release. But while configuring it I am facing issues as below > > > > > 1. When I try to provide BitBake directory as part of tool chain I > get an error that need to build meta-ide-support before configuring > it. > > > As I did build meta-ide-support before setting up the path as I can > see an environment file present under /tmp > path. > > > > You will need to provide the path to the build directory. This is the > > directory holding tmp. > > > > > 2. If I select Standard SDK option then it accepts the same i.e. it > accept environment file present under tmp directory as vaild which I > suppose it should not do. > > > 3. I already has Makefile based project which I am trying to > configure in eclipse by selecting Yocto as Toolchain. > > > But when I try to build it I am seeing its using platform GCC > instead of Yocto tool chain. > > > > Selecting the correct directory should set up the cross-compiler > > environment and fix this. > > > > > > How to fix the same as I cant change this project to an CMake based > project. > > > > > > Is there as way I can use Kepler plugin instead of Juno as when I > try the same with Luna I am getting dependencies errors. > > > > You can find the plugin releases here: > > https://urldefense.proofpoint.com/v2/url?u=http-3A__downloads.yoctoproject.org_releases_eclipse-2Dplugin_&d=AwIFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=geJ1wB7xRIMmteYB2Fo8esL32BOWvwP1HmY0YuLEB4E&m=Hg_RatI-pPFNhlwlj3rvSiP3RspGPYNzHRBg-XaXN1U&s=11DZqLCED8UtaM9vU0YxGMeaNWGlerPzTawEoVwuJd4&e= > > > > > Cheers, > > Todor > > > > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote: Hi All, I got the an error while i am checking out the linux kernel from the SVN to build in the YOCTO project environment. What release is this ? master ? An older release ? And are you seeing this same error if you have a kernel recipe that builds from git ? i.e. one of the Yocto reference boards with a similar SRCREV ? The yocto kernel's expect to be able to validate the commits and then modify the tree with additional git commands, so the tree is either in git format, or is converted to a git format (in the case of a tgz) .. so it could be that the SVN checkout is preventing that conversion from happening. Bruce Could please help me in resolving the Issue. Error log is: Log data follows: | DEBUG: Executing shell function do_validate_branches | NOTE: custom recipe is being built, forcing SRCREV to INVALID | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch | fatal: ambiguous argument 'INVALID': unknown revision or path not in the working tree. | Use '--' to separate paths from revisions | WARNING: exit code 128 from a shell command. | ERROR: Function failed: do_validate_branches (log file is located at /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) Thanks in advance. Regards, Raghavendra K. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Tuesday, April 14, 2015 2:50 PM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 55, Issue 46 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) -- Message: 1 Date: Tue, 14 Apr 2015 09:20:38 + From: Raghavendra Kakarla To: "yocto@yoctoproject.org" Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 Message-ID: <1429003199394.19...@inedasystems.com> Content-Type: text/plain; charset="iso-8859-1" Hi All, When I take kernel from the SVN I got the validation error that SRCREV is not proper. Could you please help me in resolving this issue. Thanks in advance. Regards, Raghavendra. From: yocto-boun...@yoctoproject.org on behalf of yocto-requ...@yoctoproject.org Sent: Saturday, February 21, 2015 4:04 AM To: yocto@yoctoproject.org Subject: yocto Digest, Vol 53, Issue 97 Send yocto mailing list submissions to yocto@yoctoproject.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.yoctoproject.org/listinfo/yocto or, via email, send a message with subject or body 'help' to yocto-requ...@yoctoproject.org You can reach the person managing the list at yocto-ow...@yoctoproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of yocto digest..." Today's Topics: 1. Re: Simple recipe quit working in dizzy (akuster) -- Message: 1 Date: Fri, 20 Feb 2015 14:28:10 -0800 From: akuster To: yocto@yoctoproject.org Subject: Re: [yocto] Simple recipe quit working in dizzy Message-ID: <54e7b4fa@mvista.com> Content-Type: text/plain; charset=windows-1252; format=flowed On 02/20/2015 09:49 AM, Jim Rafert wrote: Hi Paul, Thank you for taking an interest in this. I looked at the log.do_rootfs, and didn't see anything that was immediately suspicious. I have inlined the log at the end of my reply, here. I don't see how such a simple recipe could be broken by a Yocto bug, and not have the whole thing be massively broken. Is it possible for you to try your recipe on 'master'? that might tell use if something is missing in dizzy. - Armin -Jim- cat ./core-image-full-cmdline/1.0-r0/temp/log.do_rootfs DEBUG: Executing python function rootfs_process_ignore DEBUG: Python function rootfs_process_ignore finished DEBUG: Executing python function rootfs_runtime_mapping DEBUG: Python function rootfs_runtime_mapping finished DEBUG: Executing python function do_rootfs NOTE: configuring RPM platform settings NOTE: configuring RPM system provides NOTE: configuring RPM DB settings NOTE: configuring Smart settings NOTE: Note: adding Smart channel spectra_ls (35) NOTE: Note: adding Smart channel i586 (30) NOTE: Note: adding Smart channel all (25) NOTE: adding Smart RPM DB channel NOTE: Note: configuring RPM cross-install scriptlet_wrapper NOTE: ## Gene
Re: [yocto] [Dizzy] Multilib in Poky
Hi Rebecca, On Monday 13 April 2015 05:03:00 Chang, Rebecca Swee Fun wrote: > I am building a MACHINE = "qemux86" image using Poky v1.7.1 with multilib > feature. I would like the image generated to use glibc as the main libc and > uclibc in lib32 multilib. Here are my settings in build/local.conf: > > # Multilib Configurations > require conf/multilib.conf > MULTILIBS = "multilib:lib32" > DEFAULTTUNE_virtclass-multilib-lib32 = "x86" > baselib_virtclass-multilib-lib32 = "lib32" > LIBCEXTENSION_virtclass-multilib-lib32 = "-uclibc" > LIBCOVERRIDE_virtclass-multilib-lib32 = ":libc-uclibc" > PREFERRED_PROVIDER_virtual/lib32-libc ?= "uclibc" > PREFERRED_PROVIDER_virtual/lib32-libiconv ?= "libiconv" > PREFERRED_PROVIDER_virtual/lib32-libintl ?= "gettext" > USE_NLS_virtclass-multilib-lib32 ?= "no" > CXXFLAGS_append_virtclass-multilib-lib32 = " -fvisibility-inlines-hidden" > IMAGE_LINGUAS_virtclass-multilib-lib32 = "" > LIBC_DEPENDENCIES_virtclass-multilib-lib32 = "uclibc uclibc-dbg uclibc-dev > uclibc-thread-db" PTEST_ENABLED_virtclass-multilib-lib32 = "" > > > When I run BitBake to build a Sato image, Bitbake prompt the following > error. > > Parsing of 893 .bb files complete (0 cached, 893 parsed). 2181 targets, 174 > skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue > dependencies > ERROR: Nothing PROVIDES 'lib32-glibc' > ERROR: lib32-glibc was skipped: incompatible with target linux-uclibc > ERROR: Required build target 'core-image-sato' has no buildable providers. > Missing or unbuildable dependency chain was: ['core-image-sato', > 'lib32-glibc'] Summary: There were 2 ERROR messages shown, returning a > non-zero exit code. > > While the same configurations for multilib was run on Poky Daisy branch, > however we don't hit this problem. From the Reference Manual, I know that > as we migrate to YP version 1.7, eglibc 3.19 has been replaced with glibc > 2.20. Could this be the reason of the broken multilib features? > > How should I resolve this? How should I exclude the "lib32-glibc" package > from the build? Thanks in advance. I have reproduced this; it appears uclibc isn't actually being selected properly for the multilib. I've filed a bug with some details: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7607 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Mount options for /dev/root
Hi I'm trying to add some mount options to / (/dev/root) such as 'nobarrier'. What would be the best way to define this option? I know two possible ways: * rootflags boot paramenter, but I'd prefer it to be in userspace * /etc/fstab, but these options are not passed to mount. The script /etc/init.d/checkroot.sh does parse fstab and even saves the options ($rootopts), but these options are not passed to the mount command. Other implementation, such as debians checkroot.sh, do pass these options to mount. Is this by intention or a bug? Thanks & Regards, Oliver -- bytes at work Technoparkstrasse 7 CH-8406 Winterthur Switzerland phone: +41 52 213 79 79 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] dev-manual: Updated wic runtime requirements
Wic is not using parted and other runtime dependencies from host system anymore. It uses native tools instead. Removed host parted from the list of requirements. Added instructions to build native tools. Signed-off-by: Ed Bartosh --- documentation/dev-manual/dev-manual-common-tasks.xml | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index c856775..0ea4940 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -3788,12 +3788,6 @@ development host system. -The -GNU Parted -package must be installed on your development host -system. - - You need to have the build artifacts already available, which typically means that you must have already created an image using the @@ -3806,6 +3800,12 @@ in the form generated by the build system. +You must build several native tools: + + $ bitbake parted-native dosfstools-native mtools-native + + + You must have sourced one of the build environment setup scripts (i.e. &OE_INIT_FILE; -- 2.1.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build available for QA
-e A build identified as needing QA has finished on the autobuilder. This build is located at: http://autobuilder.yoctoproject.org/pub/nightly/20150414-2 Build hash information: meta-intel : 53eea4f12311b4808b3af9695ac822eea1fc60c2 meta-fsl-arm : e3cc9452aaa2895bbc8bdd7c8940b4dd2d14213e meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 4c8cd553f9de56379e2b6502ceb996521e2d6a20 poky : e9fcc570716e68a64f2a17c0e7aa79e1cd758f39 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] 1.7.1 ADT-installer errors
Hi, I can confirm it is an issue. I got a 404 not found error when I tried to download the core-image-sato-sdk-qemux86.tar.bz2 from http://adtrepo.yoctoproject.org/1.7.1/rootfs/qemux86/. Looks like the symbolic link is broken. Beth, Would you please have a look at this and fix it ? Thanks, Yi 在 2015年04月14日 16:24, heli Atck 写道: Hi, I'm new to Yocto (and embedded Linux for that matter). I was following the ADT manual to get started with application development. I tried using the ADT-installer script, but ran into some errors. Here's the relevant part of the installer log file: /Creating directory /home/spe/test-yocto/qemux86... Extracting rootfs: core-image-sato-sdk-qemux86.tar.bz2, using pseudo... tar (child): ./download_image/core-image-sato-sdk-qemux86.tar.bz2: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now/ There are no files in my /download_image directory so I guess they have not been properly retrieved from the repository. I looked at the repository for 1.7.1 at http://adtrepo.yoctoproject.org/1.7.1/rootfs/qemux86/ and some of the relevant files seem to be missing. Or did I mis a step somewhere? Sammy -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SRCREV Issue for custom linux kernel
Hi Bruce, I downloaded the yocto from the following link: git clone -b dizzy git://git.yoctoproject.org/poky.git And added the my custom recipe for downloading our custom kernel from SVN. This gives the error. Regards, Raghavendra. From: Bruce Ashfield Sent: Tuesday, April 14, 2015 5:36 PM To: Raghavendra Kakarla; yocto@yoctoproject.org Subject: Re: [yocto] SRCREV Issue for custom linux kernel On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote: > Hi All, > > I got the an error while i am checking out the linux kernel from the SVN to > build in the YOCTO project environment. > What release is this ? master ? An older release ? And are you seeing this same error if you have a kernel recipe that builds from git ? i.e. one of the Yocto reference boards with a similar SRCREV ? The yocto kernel's expect to be able to validate the commits and then modify the tree with additional git commands, so the tree is either in git format, or is converted to a git format (in the case of a tgz) .. so it could be that the SVN checkout is preventing that conversion from happening. Bruce > Could please help me in resolving the Issue. > > > Error log is: > Log data follows: > | DEBUG: Executing shell function do_validate_branches > | NOTE: custom recipe is being built, forcing SRCREV to INVALID > | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch > | fatal: ambiguous argument 'INVALID': unknown revision or path not in the > working tree. > | Use '--' to separate paths from revisions > | WARNING: exit code 128 from a shell command. > | ERROR: Function failed: do_validate_branches (log file is located at > /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852) > > > Thanks in advance. > > Regards, > > Raghavendra K. > > From: yocto-boun...@yoctoproject.org on > behalf of yocto-requ...@yoctoproject.org > Sent: Tuesday, April 14, 2015 2:50 PM > To: yocto@yoctoproject.org > Subject: yocto Digest, Vol 55, Issue 46 > > Send yocto mailing list submissions to > yocto@yoctoproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.yoctoproject.org/listinfo/yocto > or, via email, send a message with subject or body 'help' to > yocto-requ...@yoctoproject.org > > You can reach the person managing the list at > yocto-ow...@yoctoproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of yocto digest..." > > > Today's Topics: > > 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla) > > > -- > > Message: 1 > Date: Tue, 14 Apr 2015 09:20:38 + > From: Raghavendra Kakarla > To: "yocto@yoctoproject.org" > Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97 > Message-ID: <1429003199394.19...@inedasystems.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi All, > > When I take kernel from the SVN I got the validation error that SRCREV is not > proper. > > Could you please help me in resolving this issue. > > Thanks in advance. > > Regards, > Raghavendra. > > > > From: yocto-boun...@yoctoproject.org on > behalf of yocto-requ...@yoctoproject.org > Sent: Saturday, February 21, 2015 4:04 AM > To: yocto@yoctoproject.org > Subject: yocto Digest, Vol 53, Issue 97 > > Send yocto mailing list submissions to > yocto@yoctoproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.yoctoproject.org/listinfo/yocto > or, via email, send a message with subject or body 'help' to > yocto-requ...@yoctoproject.org > > You can reach the person managing the list at > yocto-ow...@yoctoproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of yocto digest..." > > > Today's Topics: > > 1. Re: Simple recipe quit working in dizzy (akuster) > > > -- > > Message: 1 > Date: Fri, 20 Feb 2015 14:28:10 -0800 > From: akuster > To: yocto@yoctoproject.org > Subject: Re: [yocto] Simple recipe quit working in dizzy > Message-ID: <54e7b4fa@mvista.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > > On 02/20/2015 09:49 AM, Jim Rafert wrote: >> Hi Paul, >> >> Thank you for taking an interest in this. >> >> I looked at the log.do_rootfs, and didn't see anything that was immediately >> suspicious. >> I have inlined the log at the end of my reply, here. >> >> I don't see how such a simple recipe could be broken by a Yocto bug, and not >> have the >> whole thing be massively broken. > > Is it possible for you to try your recipe on 'master'? that might tell > use if something is missing in dizzy. > > > - Armin >> >> -Jim- >> >> cat ./core-image-ful
Re: [yocto] SRCREV Issue for custom linux kernel
Hi Bruce,
My recipe is like following:
# oe-core kernel classes to apply a subset of yocto kernel
# management to git managed kernel repositories.
#
# Warning:
#
# Building this kernel without providing a defconfig or BSP
# configuration will result in build or boot errors. This is not a
# bug.
#
# Notes:
#
# patches: patches can be merged into to the source git tree itself,
#added via the SRC_URI, or controlled via a BSP
#configuration.
#
# example configuration addition:
#SRC_URI += "file://smp.cfg"
# example patch addition:
#SRC_URI += "file://0001-linux-version-tweak.patch
# example feature addition:
#SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
SRC_URI =
"svn://192.168.24.190:9090/svn/trunk/code/kernels;module=linux-3.10.14;protocol=http;user=admin;pswd=Welcome123"
SRC_URI += "file://defconfig"
SRC_URI += "file://arqlyn.scc \
file://arqlyn.cfg \
file://arqlyn-user-config.cfg \
file://arqlyn-user-patches.scc \
"
LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"
SRCREV = "94"
PR = "r0"
PV = "${LINUX_VERSION}"
S = "${WORKDIR}/linux-3.10.14"
COMPATIBLE_MACHINE_arqlyn = "arqlyn"
Regards,
Raghavendra
From: Bruce Ashfield
Sent: Tuesday, April 14, 2015 5:36 PM
To: Raghavendra Kakarla; yocto@yoctoproject.org
Subject: Re: [yocto] SRCREV Issue for custom linux kernel
On 2015-04-14 6:48 AM, Raghavendra Kakarla wrote:
> Hi All,
>
> I got the an error while i am checking out the linux kernel from the SVN to
> build in the YOCTO project environment.
>
What release is this ? master ? An older release ?
And are you seeing this same error if you have a kernel recipe
that builds from git ? i.e. one of the Yocto reference boards
with a similar SRCREV ?
The yocto kernel's expect to be able to validate the commits
and then modify the tree with additional git commands, so the
tree is either in git format, or is converted to a git format
(in the case of a tgz) .. so it could be that the SVN checkout
is preventing that conversion from happening.
Bruce
> Could please help me in resolving the Issue.
>
>
> Error log is:
> Log data follows:
> | DEBUG: Executing shell function do_validate_branches
> | NOTE: custom recipe is being built, forcing SRCREV to INVALID
> | NOTE: SRCREV validation skipped for AUTOREV or empty meta branch
> | fatal: ambiguous argument 'INVALID': unknown revision or path not in the
> working tree.
> | Use '--' to separate paths from revisions
> | WARNING: exit code 128 from a shell command.
> | ERROR: Function failed: do_validate_branches (log file is located at
> /home/testuser/poky/build/tmp/work/dhruva-poky-linux/linux-yocto-custom/3.10.14-r0/temp/log.do_validate_branches.6852)
>
>
> Thanks in advance.
>
> Regards,
>
> Raghavendra K.
>
> From: yocto-boun...@yoctoproject.org on
> behalf of yocto-requ...@yoctoproject.org
> Sent: Tuesday, April 14, 2015 2:50 PM
> To: yocto@yoctoproject.org
> Subject: yocto Digest, Vol 55, Issue 46
>
> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. Re: yocto Digest, Vol 53, Issue 97 (Raghavendra Kakarla)
>
>
> --
>
> Message: 1
> Date: Tue, 14 Apr 2015 09:20:38 +
> From: Raghavendra Kakarla
> To: "yocto@yoctoproject.org"
> Subject: Re: [yocto] yocto Digest, Vol 53, Issue 97
> Message-ID: <1429003199394.19...@inedasystems.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi All,
>
> When I take kernel from the SVN I got the validation error that SRCREV is not
> proper.
>
> Could you please help me in resolving this issue.
>
> Thanks in advance.
>
> Regards,
> Raghavendra.
>
>
>
> From: yocto-boun...@yoctoproject.org on
> behalf of yocto-requ...@yoctoproject.org
> Sent: Saturday, February 21, 2015 4:04 AM
> To: yocto@yoctoproject.org
> Subject: yocto Digest, Vol 53, Issue 97
>
> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please e
