Re: [yocto] ERROR: problem:package openssh-7.6p1-r0.i586 conflicts with dropbear provided by dropbear-2017.75-r0.i586
Add this to local.conf PACKAGE_EXCLUDE += " packagegroup-core-ssh-dropbear" *Thanks,* *Sandeep* On Mon, Apr 2, 2018 at 4:38 AM, Aditya Tayadewrote: > Hi, > > > I trying to build core-image-sato using yocto 2.5 with new package openssh. > > > Added openssh entry in the local.conf file as follows: > > IMAGE_INSTALL_append = "openssh" > > > But facing some conflicts error. Please refer attached log file for more > information. > > > Could you please help to resolve the issue. I need to use use openssh for > ssh rather than dropbear. > > > > Regards, > > Aditya Tayade > This message contains information that may be privileged or confidential > and is the property of the KPIT Technologies Ltd. It is intended only for > the person to whom it is addressed. If you are not the intended recipient, > you are not authorized to read, print, retain copy, disseminate, > distribute, or use this message or any part thereof. If you receive this > message in error, please notify the sender immediately and delete all > copies of this message. KPIT Technologies Ltd. does not accept any > liability for virus infected mails. > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Problems to build xen-guest-image-minimal
On Wed, May 31, 2017 at 10:13 AM, Khem Rajwrote: > > On Wed, May 31, 2017 at 12:22 AM Pello Heriz < > pello.he...@alumni.mondragon.edu> wrote: > >> Hi, >> >> I'm trying to build xen-guest-image-minimal with master branch of Yocto, >> but I keep stuck in the next error: >> >> bitbake xen-guest-image-minimal >> NOTE: /opt/yocto_GE/poky/meta-qt5/recipes-qt/qt5/qtbase_git.bb: >> base_contains is deprecated, please use bb.utils.contains instead. >> NOTE: /opt/yocto_GE/poky/meta-qt5/recipes-qt/qt5/qtbase_git.bb: >> base_contains is deprecated, please use bb.utils.contains instead. >> WARNING: /opt/yocto_GE/poky/meta-petalinux/recipes-external/ >> external-xilinx-toolchain/libgcc-xilinx.bb: LICENSE_libgcov-dev includes >> licenses (GPL-3.0) that are not listed in LICENSE >> Parsing recipes: 100% |##| Time: >> 0:04:34 >> Parsing of 2477 .bb files complete (0 cached, 2477 parsed). 3310 targets, >> 312 skipped, 0 masked, 0 errors. >> WARNING: No recipes available for: >> /opt/yocto_GE/poky/meta-petalinux/recipes-devtools/ >> python/python-smartpm_%.bbappend >> WARNING: No bb files matched BBFILE_PATTERN_gpe-layer >> '^/opt/yocto_GE/poky/meta-openembedded/meta-gpe/' >> NOTE: Resolving any missing task queue dependencies >> ERROR: Nothing PROVIDES 'rpmresolve-native'. Close matches: >> meson-native >> rpm-native >> perl-native >> ERROR: Required build target 'xen-guest-image-minimal' has no buildable >> providers. >> Missing or unbuildable dependency chain was: ['xen-guest-image-minimal', >> 'rpmresolve-native'] >> > > It's possible that you do not have matching releases of various layers I > would first check that > Yes master is not stable you need to clone rel-v2017.1 tag > >> >> >> The bblayers that I have included to the project are the next ones: >> >> BBLAYERS ?= " \ >> ${MY_META_DIR}/meta \ >> ${MY_META_DIR}/meta-poky \ >> ${MY_META_DIR}/meta-yocto-bsp \ >> ${MY_META_DIR}/meta-openembedded/meta-perl \ >> ${MY_META_DIR}/meta-openembedded/meta-systemd \ >> ${MY_META_DIR}/meta-openembedded/meta-gpe \ >> ${MY_META_DIR}/meta-openembedded/meta-python \ >> ${MY_META_DIR}/meta-openembedded/meta-efl \ >> ${MY_META_DIR}/meta-openembedded/meta-ruby \ >> ${MY_META_DIR}/meta-openembedded/meta-filesystems \ >> ${MY_META_DIR}/meta-openembedded/meta-gnome \ >> ${MY_META_DIR}/meta-openembedded/meta-multimedia \ >> ${MY_META_DIR}/meta-openembedded/meta-networking \ >> ${MY_META_DIR}/meta-openembedded/meta-webserver \ >> ${MY_META_DIR}/meta-openembedded/meta-xfce \ >> ${MY_META_DIR}/meta-openembedded/meta-initramfs \ >> ${MY_META_DIR}/meta-openembedded/meta-oe \ >> ${MY_META_DIR}/meta-qt5 \ >> ${MY_META_DIR}/meta-selftest \ >> ${MY_META_DIR}/meta-skeleton \ >> ${MY_META_DIR}/meta-xilinx \ >> ${MY_META_DIR}/meta-xilinx-tools \ >> ${MY_META_DIR}/meta-petalinux \ >> ${MY_META_DIR}/meta-virtualization \ >> ${MY_META_DIR}/meta-xzd \ >> " >> >> How can I solve this issue? >> >> Regards, >> Pello >> >> >> >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] OpenEmbedded Developers Meeting in Portland before ELC
Hi Philip, Is Yocto developer day planned during ELC-2017 Portland, USA. Can you share the registration details if any? On Mon, Jan 9, 2017 at 2:04 PM, Philip Balisterwrote: > As we do around each Embedded Linux Conference, OpenEmbedded will host a > developer meeting to discuss the state of OpenEmbedded and what efforts > we should focus on over the next six months or so. > > All developers and users are welcome to attend. We like to hear feedback > from a variety of people over what works, doesn't work, and is useful to > people using OpenEmbedded for all sort of applications. > > The meeting will be held Monday, Feb 20 at a location we can almost > announce. Based on prior years, the meeting will run from 9AM to 5PM. > > If you are going to attend add your name to: > > http://openembedded.org/wiki/OEDAM_2017 > > Also, go ahead and add ideas for the agenda. We'll organize them better > just before the actual meeting. > > See you all in Portland, > > Philip > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- *Thanks & Regards,* *Sandeep G R* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Clarification regarding GCC tool version supported on - Krogoth 2.1.1
Hi Vijay, You can run *"bitbake-layers show-recipes | grep gcc-source"* to know more on supported toolchain versions. On Wed, Oct 12, 2016 at 11:55 AM, Vijayakumar Badiger < vijayakuma...@gmail.com> wrote: > Thanks Paul, appreciate your reply. > > Cheers, > Vijay > > > On Mon, Oct 10, 2016 at 6:24 PM, Paul Eggleton < > paul.eggle...@linux.intel.com> wrote: > >> Hi Vijay, >> >> On Mon, 10 Oct 2016 17:44:13 Vijayakumar Badiger wrote: >> > Please can some one tell me the tool chain versions supported on the >> latest >> > YPCore-Krogoth. >> > I know the it uses default GCC5.3, just wanted to know if older tool >> chain >> > like 4.9XX is supported or not. >> > >> > I don't see the feature list like the one listed below for Krogoth >> 2.1.1. >> > which clearly states the tool chain versions supported. >> > >> > https://www.yoctoproject.org/downloads/core/jethro20 >> >> gcc 4.9 is included in the krogoth branch, and being an earlier default >> version it should work - however it's fair to say it does not receive the >> same >> level of testing that 5.3 does given that 5.3 is the default. >> >> Cheers, >> Paul >> >> -- >> >> Paul Eggleton >> Intel Open Source Technology Centre >> > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- *Thanks & Regards,* *Sandeep G R* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Reg flashing Yocto SDcard image onto IMX6q sabre sd card
Hi Shalini, Below is the basic steps for SD card boot on iMX6. Create two partitions on the SD card ext2 for boot and ext4 for rootfs using following commands. *Create the partions:* *sudo dd if=/dev/zero of=/dev/sdX bs=1M count=16* *sudo mkfs.ext2 /dev/sdX1 -L boot* *sudo mkfs.ext4 /dev/sdX2 -L rootfs* *Mount the partions:* *sudo mkdir -p /media/boot/* *sudo mkdir -p /media/rootfs/* *sudo mount /dev/sdX1 /media/boot/* *sudo mount /dev/sdX2 /media/rootfs/* *Copy the binaries to SD card:* *sudo tar xfvp yocto-build/tmp/deploy/rootfs.tar -C /media/rootfs/* *sudo cp -v yocto-build/tmp/deploy/kernel-image /media/boot* *sudo cp -v yocto-build/tmp/deploy/kernel-dtb /media/boot* *Edit the fstab file as shown below:* *sudo nano /media/rootfs/etc/fstab* */dev/sdX2 / auto errors=remount-ro 0 1* */dev/sdX1 /boot/uboot auto defaults 0 2* Make sure your uboot environment variables are set properly for sd card flash. On Mon, Apr 6, 2015 at 6:23 AM, Shalini K P shalini...@lnttechservices.com wrote: Hi, I have prepared an Yocto SD card image core-image-minimal-imx6q-sabresd.sdcard. I trying to flash the image onto sdcard using the command *sudo dd if= core-image-minimal-imx6q-sabresd.sdcard of=/dev/sdb bs=1M* *Sync* *Sync* I m getting the boot messages as below *U-Boot 2014.10+fslc+g5fd0b60 (Apr 03 2015 - 18:55:01) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: MX6-SabreSD I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2 *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In:serial Out: serial Err: serial PMIC: PFUZE100 ID=0x10 Net: FEC [PRIME] Hit any key to stop autoboot: 1 * I m stuck up badly. It is not going further. Does the sdcard image contain ü-boot, kernel image and rootfs ? or should I flash u-boot separately ? I even tried flashing both u-boot and sdcaed image. But getting same messages. Request help in this regard. I'm using Dizzy branch and SABRESD Evk board. Thanks Regards Shalini K P *LT Technology Services Ltd* www.LntTechservices.com http://www.lnttechservices.com/ This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- *Thanks Regards,* *Sandeep G R* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] regarding yocto installation
Hi Shalini, Your repo url in not a valid one ( https://dl-ssl.google.com/dl/googlesource/git-repo/repo) Please follow this link https://github.com/Freescale/fsl-community-bsp-platform On Mon, Dec 8, 2014 at 1:57 AM, Shalini K P shalini...@lnttechservices.com wrote: Hi, M trying to install yocto on host Ubuntu 12.04. I m following these steps. mkdir ~/bin $ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo ~/bin/repo $ chmod a+x ~/bin/repo $ PATH=${PATH}:~/bin * Download the BSP metadata (recipes + configuration files + classes) $ mkdir fsl-community-bsp $ cd fsl-community-bsp fsl-community-bsp $ repo init \ -u https://github.com/Freescale/fsl-community-bsp-platform \ -b dylan fsl-community-bsp $ repo sync *Fetching project meta-fsl-arm-extra* *Fetching project poky* *Fetching project meta-fsl-arm* *Fetching project meta-openembedded* *Fetching projects: 16% (1/6) Fetching project fsl-community-bsp-base* After this it does not proceed further. Can anyone please help me how to proceed further. Regards Shalini *LT Technology Services Ltd* www.LntTechservices.com http://www.lnttechservices.com/ This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- *Thanks Regards,* *Sandeep G R* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Losing Ethernet after reboot
Rick, Check the interface using the command ifconfig -a, then add the corresponding interface in /etc/network/interfaces and restart the network services. On Tue, Mar 18, 2014 at 10:42 AM, Rick Bianchi bianchirickku...@gmail.comwrote: Sorry typing on the fly. Here is what is in interfaces: auto eth0 iface eth0 inet dhcp On Tue, Mar 18, 2014 at 9:17 AM, Gary Thomas g...@mlbassoc.com wrote: On 2014-03-18 10:10, Rick Bianchi wrote: I losing Ethernet after every reboot. What is the process to have it come up manually? Image: Dylan gumstix-console I have already added eth0 auto to my /etc/network/interfaces. Shouldn't this line read auto eth0 not the other way around? At the moment I need to run the following after every reboot: ifconfig eth0 up udhcpc eth0 -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- *Thanks Regards,* *Sandeep G R* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Openvswitch integration in yocto
Hi Sonia, Add this line IMAGE_INSTALL_append += openvswitch to * QorIQ-SDK-V1.4-20130814-yocto/meta-fsl-networking/images/fsl-image-core.bb.* * * And do step 3 and openvswitch will be on T4240QDS. On Tue, Oct 29, 2013 at 4:11 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Hi Sonia, On Tuesday 29 October 2013 12:33:04 sonia verma wrote: For compiling openvswitch i perform following steps:- 1. bitbake -f -c compile openvswitch. 2. bitbake openvswitch. 3. bitbake fsl-image-core. but when i get fsl-image-core-t4240rdb-20131028123337.rootfs.ext2.gz.u-boot boot the board with uImage above file system i did not find any openvswitch utilities. can you please guide me to how to integrate openvswitch in yocto. If you wish openvswitch to be included in your image you will need to add it explicitly - see this section of the manual: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Once you have done this, steps 1 and 2 are no longer necessary. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- *Thanks Regards,* *Sandeep G R* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to bring up apt and dpkg packages on yocto
Hi Paul, I have made those changes as PACKAGE_CLASSES ?= package_deb IMAGE_FEATURES += package-management IMAGE_INSTALL_append += dpkg but ended with an error and attached a log file for reference. I have attached the log for reference. On Mon, Oct 28, 2013 at 5:05 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Tuesday 22 October 2013 08:10:15 Sandeep G.R wrote: I have selected PACKAGE_CLASSES ?= package_rpm package_deb and IMAGE_FSTYPE is tar.gz package_deb must be listed first in PACKAGE_CLASSES if you wish to use it for constructing your image. You will also need to have package-management in IMAGE_FEATURES if you want apt/dpkg and the package manager data to be installed into the image itself. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- *Thanks Regards,* *Sandeep G R* sda-14@sandeep:~/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto$ source fsl-setup-poky -m t4240qds-64b -j4 -t4 Configuring for t4240qds-64b board type Creating an yocto build output at /home/sda-14/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds-64b_release Run the following commands to start a build: bitbake fsl-image-core bitbake fsl-image-kvm bitbake fsl-image-flash bitbake fsl-image-minimal bitbake fsl-image-lsb-sdk bitbake fsl-image-full To return to this build environment later please run: source /home/sda-14/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds-64b_release/SOURCE_THIS sda-14@sandeep:~/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds-64b_release$ bitbake fsl-image-full Pseudo is not present but is required, building this first before the main build Parsing recipes: 100% |#| Time: 00:02:26 Parsing of 1363 .bb files complete (0 cached, 1363 parsed). 3119 targets, 128 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= powerpc64-fsl_networking-linux MACHINE = t4240qds-64b DISTRO= fsl-networking DISTRO_VERSION= 1.4 TUNE_FEATURES = m64 fpu-hard e6500 altivec TARGET_FPU= hard meta meta-yocto meta-yocto-bsp= sdk-v1.4.x:5a7532143a49f59a5c85b08d3daf574fb1eccd8d meta-fsl-ppc = sdk-v1.4.x:f9fd0a617eb6913f87335c551918315ff4ebe18c meta-fsl-ppc-toolchain = sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723 meta-virtualization = sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93 meta-fsl-networking = (nobranch):00f7a535029ca7ef8c96ba8e9916d4742166bab0 meta-oe meta-networking = sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616 NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 63 tasks of which 63 didn't need to be rerun and all succeeded. No currently running tasks (2 of 9) Loading cache: 100% |###| ETA: 00:00:00 Loaded 3120 entries from dependency cache. Build Configuration: BB_VERSION= 1.18.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Ubuntu-12.04 TARGET_SYS= powerpc64-fsl_networking-linux MACHINE = t4240qds-64b DISTRO= fsl-networking DISTRO_VERSION= 1.4 TUNE_FEATURES = m64 fpu-hard e6500 altivec TARGET_FPU= hard meta meta-yocto meta-yocto-bsp= sdk-v1.4.x:5a7532143a49f59a5c85b08d3daf574fb1eccd8d meta-fsl-ppc = sdk-v1.4.x:f9fd0a617eb6913f87335c551918315ff4ebe18c meta-fsl-ppc-toolchain = sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723 meta-virtualization = sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93 meta-fsl-networking = (nobranch):00f7a535029ca7ef8c96ba8e9916d4742166bab0 meta-oe meta-networking = sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616 NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_rootfs (see /home/sda-14/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds-64b_release/tmp/work/t4240qds_64b-fsl_networking-linux/fsl-image-full/1.0-r22/temp/log.do_rootfs.30800 for further information) ERROR: Logfile of failure stored in: /home/sda-14/sdk-1.4-source/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds-64b_release/tmp/work/t4240qds_64b-fsl_networking-linux/fsl-image-full/1.0-r22/temp/log.do_rootfs.30800 Log data follows: | DEBUG: Executing shell function do_rootfs | dpkg-scanpackages: info: Wrote 53 entries to output Packages file. | dpkg-scanpackages: info: Wrote 6106 entries to output Packages file. | dpkg-scanpackages: info: Wrote 74 entries to output Packages file. | dpkg-scanpackages: info: Wrote 53 entries to output
Re: [yocto] How to bring up apt and dpkg packages on yocto
Hi, I have selected PACKAGE_CLASSES ?= package_rpm package_deb and IMAGE_FSTYPE is tar.gz On Mon, Oct 21, 2013 at 11:05 PM, Gaurang Shastri gmshas...@gmail.comwrote: hi, what packaging method you have selected while creating your image ?? //Gaurang Shastri On Tue, Oct 22, 2013 at 4:36 AM, Sandeep G.R grsandee...@gmail.comwrote: Hi All, I have ported Embedded Linux using yocto opensource for Freescale QorIQ T4240QDS processor. I need to bring up apt and dpkg on T4240QDS using yocto. For this i need to modify in some .conf or .bb files. Can you please let me know in which files i need to do these changes in order to bring up apt and dpkg on T4240QDS using yocto. -- *Thanks Regards,* *Sandeep G R* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- *Thanks Regards,* *Sandeep G R* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to bring up apt and dpkg packages on yocto
Hi All, I have ported Embedded Linux using yocto opensource for Freescale QorIQ T4240QDS processor. I need to bring up apt and dpkg on T4240QDS using yocto. For this i need to modify in some .conf or .bb files. Can you please let me know in which files i need to do these changes in order to bring up apt and dpkg on T4240QDS using yocto. -- *Thanks Regards,* *Sandeep G R* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto