[yocto] kernel build in Yocto version 2.5 (sumo)
Dear Yocto team, Linux kernel image build in Yocto version 2.5 is giving following error. Freeing unused kernel memory: 2048K (8080 - 80a0) *Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP THUMB2* Modules linked in: CPU: 0 PID: 1 Comm: init Not tainted 4.9.0-rt1 #1 Hardware name: Renesas RZ/N1 (DT) task: be07 task.stack: be078000 PC is at ret_fast_syscall+0x2/0x4a LR is at SyS_brk+0xaf/0xec pc : [<802130a2>]lr : [<80288523>]psr: 6013 sp : be079fa8 ip : be07 fp : 1000 r10: r9 : be078000 r8 : 80213264 r7 : 002d r6 : 76f92068 r5 : 00010034 r4 : 0008 r3 : 76fc0f38 r2 : 00040900 r1 : r0 : 00027000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 70c5387d Table: be613900 DAC: fffd Process init (pid: 1, stack limit = 0xbe078218) Stack: (0xbe079fa8 to 0xbe07a000) 9fa0: 0008 00010034 0001 76fc0f38 9fc0: 0008 00010034 76f92068 002d 0001 0001 1000 9fe0: 0001 7e8cee4c 76fa8864 76fa9688 2010 Code: b672 (1000f8d9) ---[ end trace 0002 ]--- *Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b* core-image-minimal image using as a root file system. *Same kernel recipe build in the Yocto 2.2.2 version is working fine.* one difference observed in the 2.5 and 2.2.2 kernel build image boot is build pc name coming as (graco_sm@build) and (oe-user@oe-host) respectively. Both the Yocto 2.5 and 2.2.2 building in the same pc graco_sm, in 2.5 version taking as oe-user@oe-host, what could be the reason for this ? 2.5 Linux build : Linux version 4.9.0-rt1 (oe-user@oe-host) (gcc version 7.3.0 (GCC) ) #1 SMP PREEMPT RT Fri Sep 7 06:53:17 UTC 2018 2.2.2 Linux build : Linux version 4.9.0-rt1 (graco_sm@build) (gcc version 6.2.0 (GCC) ) #1 SMP PREEMPT RT Wed Aug 29 19:09:12 IST 2018 For your reference attached the both version kernel boot log files kernel_yocto_2.2.2.txt and kernel_yocto_2.5.txt. Attached the linux recipes files. Kindly help us to resolve this issue. Thanks and Regards, Ravikiran J J ** BOOTLOADER STAGE0 for RZN1 ** Boot ROM Version 02.00 Boot source: QSPI STATUS: Valid SPKG header not found (100 QSPI Flash 256-byte blocks read) STATUS: Valid SPKG header not found (200 QSPI Flash 256-byte blocks read) STATUS: Valid SPKG header not found (300 QSPI Flash 256-byte blocks read) STATUS: Valid SPKG header not found (400 QSPI Flash 256-byte blocks read) STATUS: Valid SPKG header not found (500 QSPI Flash 256-byte blocks read) 00 BOOTLOADER STAGE0 Success *** Bootloader stage0 END *** *** Execute 2nd Stage Bootloader which has been loaded and verified *** U-Boot 2017.01-00100-g1022dcc (Sep 05 2018 - 16:05:30 +0530) Model: RZ/N1D GRACO Board DRAM: 1 GiB MMC: sdhci@0x4010: 0, sdhci@0x40101000: 1 SF: Detected is25lq016b with page size 256 Bytes, erase size 64 KiB, total 2 MiB, mapped at 1000 In:serial@0x4006 Out: serial@0x4006 Err: serial@0x4006 WATCHDOG REBOOT: NO WATCHDOG timer set to 3 minutes Net: dwmac.4400, dwmac.44002000 Hit any key to stop autoboot: 5 0 Enter password : * Password fine!! SF: Detected is25lq016b with page size 256 Bytes, erase size 64 KiB, total 2 MiB, mapped at 1000 Erasing SPI flash...Writing to SPI flash...done WATCHDOG timer set to 30 minutes Password entry successful => boot reading uImage-rzn1d400-graco-no-cm3.dtb 45489 bytes read in 19 ms (2.3 MiB/s) reading uImage-rzn1d400-graco.bin 3982248 bytes read in 231 ms (16.4 MiB/s) ## Booting kernel from Legacy Image at 80008000 ... Image Name: Linux-4.9.0-rt1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3982184 Bytes = 3.8 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80fe Booting using the fdt blob at 0x80fe Loading Kernel Image ... OK Loading Device Tree to bfff1000, end b1b0 ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Booting Linux on physical CPU 0x0 Linux version 4.9.0-rt1 (graco_sm@build) (gcc version 6.2.0 (GCC) ) #1 SMP PREEMPT RT Wed Aug 29 19:09:12 IST 2018 CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=70c5387d CPU: div instructions available: patching division code CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache OF: fdt:Machine model: RZ/N1D GRACO Board bootconsole [earlycon0] enabled Memory policy: Data cache writealloc percpu: Embedded 14 pages/cpu @bf7aa000 s26144 r8192 d23008 u57344 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096 Kernel command line: ip=192.168.15.39:eth0 clk_ignore_unused rootfstype=ext4 root=/dev/mmcblk0p2 rootwait console=ttyS0,115200 earlyprintk PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table
Re: [yocto] ERROR: No manifest generated
On Thu, Sep 6, 2018 at 1:47 AM, Khem Raj wrote:
>
>
> On 9/4/18 10:39 PM, Ravikiran J wrote:
> > Dear Yocto team,
> >
> > We have developed some recipe file to install the firmware binary in
> > the file system of Yocto.
> > Recipe file is working fine in *Yocto morty* version but when we tried
> > the same in the *Yocto sumo* version we got the following error for
> > *bitbake core-image-minimal*.
> >
> > *ERROR: core-image-minimal-1.0-r0 do_rootfs: No manifest generated from:
> > rtl-firmware in
> > /home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-L
> inux/sumo/poky/meta-graco/recipes-graco/firmware/rtl-firmware.bb
> > <http://rtl-firmware.bb>*
> > ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> > ERROR: Logfile of failure stored in:
> > /home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-L
> inux/sumo/poky/build/tmp/work/rzn1d400_graco-poky-linux-gnue
> abi/core-image-minimal/1.0-r0/temp/log.do_rootfs.28035
> > ERROR: Task
> > (/home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-
> Linux/sumo/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs)
> > failed with exit code '1'
> >
> >
>
> which version of yocto project release is in use here ?
>
*Yocto version 2.5*
>
> > Recipe file*rtl-firmware.bb <http://rtl-firmware.bb> *content*
> > *
> > *
> > *
> > DESCRIPTION = "RTL 8723BU BT firmware"
> >
> > LICENSE = "MIT"
> > LIC_FILES_CHKSUM =
> > "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
> >
> > PACKAGE_ARCH = "all"
>
> perhaps using inherit allarch is better here.
>
> >
> > SRC_URI += " \
> > file://rtl8723b_fw.bin \
> > "
> >
> > do_install () {
> > install -d ${D}${base_libdir}/firmware/
> > install -m 755 ${WORKDIR}/rtl8723b_fw.bin
> ${D}${base_libdir}/firmware/
> > }
> >
> > FILES_${PN} += " \
> > ${base_libdir}/firmware/rtl8723b_fw.bin \
> > "*
> > *
> >
> > What needs to be done for to avoiding manifest error ?
> > Kindly help us to resolve this issue.s
> >
> >
> > Thanks and Regards,
> > Ravikiran J J
> >
> >
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] ERROR: No manifest generated
Dear Yocto team,
We have developed some recipe file to install the firmware binary in the
file system of Yocto.
Recipe file is working fine in *Yocto morty* version but when we tried the
same in the *Yocto sumo* version we got the following error for *bitbake
core-image-minimal*.
*ERROR: core-image-minimal-1.0-r0 do_rootfs: No manifest generated from:
rtl-firmware in
/home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-Linux/sumo/poky/meta-graco/recipes-graco/firmware/rtl-firmware.bb
<http://rtl-firmware.bb>*
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-Linux/sumo/poky/build/tmp/work/rzn1d400_graco-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.28035
ERROR: Task
(/home/graco_sm/1.4.4/GRACO_SM_REL_V1.1/Software/U-Boot-and-Linux/sumo/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs)
failed with exit code '1'
Recipe file* rtl-firmware.bb <http://rtl-firmware.bb> *content
DESCRIPTION = "RTL 8723BU BT firmware"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
PACKAGE_ARCH = "all"
SRC_URI += " \
file://rtl8723b_fw.bin \
"
do_install () {
install -d ${D}${base_libdir}/firmware/
install -m 755 ${WORKDIR}/rtl8723b_fw.bin ${D}${base_libdir}/firmware/
}
FILES_${PN} += " \
${base_libdir}/firmware/rtl8723b_fw.bin \
"
What needs to be done for to avoiding manifest error ?
Kindly help us to resolve this issue.
Thanks and Regards,
Ravikiran J J
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Systemd based image freezing issue
Dear Yocto team, We have build the systemd init based core-image-minimal image in Yocto version 2.2.2 Morty. We are getting some systemd init failure with this image in our board. Following is the failed logs : systemd[1]: System time before build time, advancing clock. systemd[1]: systemd 230 running in system mode. (-PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) systemd[1]: Detected architecture arm. Welcome to Poky (Yocto Project Reference Distro) 2.2.2 (morty)! systemd[1]: Set hostname to . systemd[1]: Initializing machine ID from random generator. systemd[1]: Installed transient /etc/machine-id file. systemd[1]: Cannot determine cgroup we are running in: No medium found systemd[1]: Failed to allocate manager object: No medium found [!!] Failed to allocate manager object, freezing. systemd[1]: Freezing execution. Kernel (Version 4.9) is build with CGROUPS enable, still it's not helping to initialize properly. Systemd is enabled through the local.conf file of the build with following options : DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" Note: *Systvinit based core-image-minimal image is working fine in our board.* Is there anything else needs to enable on the Linux kernel side and Yocto side build? Kindly help us to resolve this issue. Thanks and Regards, Ravikiran J J -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ERROR: libreoffice-5.0.5.2-r0 do_package
Hi Everybody,
I am trying to build the libreoffice packages, but i am getting following
errors.
*ERROR: libreoffice-5.0.5.2-r0 do_package: QA Issue: File
'/usr/lib/libreoffice/share/extensions/mysql-connector-ooo/libmysqlclient_r.so'
from libreoffice was already stripped, this will prevent future debugging!
[already-stripped]*
WARNING: libreoffice-5.0.5.2-r0 do_package: libreoffice language file
pattern not found: /usr/lib/libreoffice/share/template/%{1}
*ERROR: libreoffice-5.0.5.2-r0 do_package: Fatal QA errors found, failing
task.ERROR: libreoffice-5.0.5.2-r0 do_package: Function failed:
do_packageERROR: Logfile of failure stored in:
/home/kamama-yocto/yocto/poky/build/tmp/work/cortexa15hf-neon-poky-linux-gnueabi/libreoffice/5.0.5.2-r0/temp/log.do_package.23588*
*ERROR: Task
(/home/kamama-yocto/yocto/poky/meta-packages/meta-office/recipes-libreoffice/libreoffice/libreoffice.bb:do_package)
failed with exit code '1'*
NOTE: Tasks Summary: Attempted 8443 tasks of which 8385 didn't need to be
rerun and 1 failed.
Summary: 1 task failed:
/home/kamama-yocto/yocto/poky/meta-packages/meta-office/recipes-libreoffice/libreoffice/libreoffice.bb:
do_package
Summary: There were 2 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
what is the issue and how to solve this ?
Best Regards,
Ravikiran
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] restricted license not whitelisted in LICENSE_FLAGS_WHITELIST
Thank you Ross, I checked my recipe file and added the LICENSE_FLAGS_WHITELIST="commercial" local.conf file, Now it's building properly. Regards, Ravikiran -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] restricted license not whitelisted in LICENSE_FLAGS_WHITELIST
Hi everybody, I am trying to build the gstreamer packages , But i am getting following erros. *bitbake gstreamer1.0-libav* ERROR: Nothing PROVIDES 'gstreamer1.0-libav' ERROR: gstreamer1.0-libav was skipped: *because it has a restricted license not whitelisted in LICENSE_FLAGS_WHITELIST* ERROR: gstreamer1.0-libav was skipped: because it has a restricted license not whitelisted in LICENSE_FLAGS_WHITELIST what is this license errors ? what may be the problem, how to solve this ? Thanks and Regards, Ravikiran -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Missing or unbuildable dependency chain
Hi everybody, I am trying to change the packagegroup from packagegroup-core-base to packagegroup-core-extende in core-image-minimal-xfce recipe file in meta-xfce layer. But i am getting following errors. ERROR: Nothing RPROVIDES 'dnsmasq' (but /home/kamama-yocto/yocto/poky/meta-openembedded/meta-oe/recipes-connectivity/networkmanager/ networkmanager_1.0.12.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'dnsmasq' is unbuildable, removing... Missing or unbuildable dependency chain was: ['dnsmasq'] NOTE: Runtime target 'networkmanager-dev' is unbuildable, removing... Missing or unbuildable dependency chain was: ['networkmanager-dev', 'dnsmasq'] NOTE: Runtime target 'networkmanager' is unbuildable, removing... Missing or unbuildable dependency chain was: ['networkmanager', 'dnsmasq'] NOTE: Runtime target 'xfce4-power-manager-dev' is unbuildable, removing... Missing or unbuildable dependency chain was: ['xfce4-power-manager-dev', 'networkmanager', 'dnsmasq'] NOTE: Runtime target 'xfce4-powermanager-plugin' is unbuildable, removing... Missing or unbuildable dependency chain was: ['xfce4-powermanager-plugin', 'networkmanager', 'dnsmasq'] NOTE: Runtime target 'packagegroup-xfce-extended' is unbuildable, removing... Missing or unbuildable dependency chain was: ['packagegroup-xfce-extended', 'xfce4-powermanager-plugin', 'networkmanager', 'dnsmasq'] ERROR: Required build target 'core-image-minimal-xfce' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal-xfce', 'packagegroup-xfce-extended', 'xfce4-powermanager-plugin', 'networkmanager', 'dnsmasq'] How to solve this problem ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs:
Sorry i forgot to add yocto list while replying. what about above error , how we can solve that problem ? On Thu, Mar 16, 2017 at 12:29 PM, Josef Holzmayr < holzm...@rsi-elektrotechnik.de> wrote: > Again, please keep your responses on the list! > > On 16.03.2017 07:52, ravikiran j wrote: > >> >> Suppose if i want to install some packages from debian or ubuntu >> repositories, >> how can i achieve that using rpm or ipk based distribution ? >> > > In short, not at all. This is not how things are meant to be. Just because > something comes in a package of a specific format, it does not mean that > you can use it everywhere the package management uses the same format. > > The correct way is to write recipes for the things that you want and > properly package them up using bitbake. > > > Greetz > -- > Josef Holzmayr > Software Developer Embedded Systems > > Tel: +49 8444 9204-48 > Fax: +49 8444 9204-50 > > R-S-I Elektrotechnik GmbH & Co. KG > Woelkestrasse 11 > D-85301 Schweitenkirchen > www.rsi-elektrotechnik.de > ——— > Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393 > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg > Ust-IdNr: DE 128592548 > > _ > Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363 > Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg > USt-IdNr.: DE 128592548 > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs:
Hi everybody, I am able to build the* core-image-minimal-xfce* image with *rpm *package management but , if i change the package-management from* rpm to deb* in local.conf file i am getting followling errors. ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs: Unable to install packages. Command '/home/kamama-yocto/yocto/poky/build-xfce-deb/tmp/sysroots/x86_64-linux/usr/bin/apt-get install --force-yes --allow-unauthenticated packagegroup-xfce-base packagegroup-core-boot run-postinsts kernel-modules packagegroup-core-x11' returned 100: Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: packagegroup-core-x11 : Depends: packagegroup-core-x11-utils but it is not going to be installed E: Unable to correct problems, you have held broken packages. ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/kamama-yocto/yocto/poky/build-xfce-deb/tmp/work/odroid_xu3-poky-linux-gnueabi/core-image-minimal-xfce/1.0-r0/temp/log.do_rootfs.162762 ERROR: Task (/home/kamama-yocto/yocto/poky/meta-openembedded/meta-xfce/recipes-core/images/core-image-minimal-xfce.bb:do_rootfs) failed with exit code '1' How to solve this problem ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] arm-poky-linux-gnueabi-gcc: Command not found
I am trying to build the linux kernel for odorid-xu3 board but i am getting following errors for *bitbake linux-stable* DEBUG: Executing shell function do_compile NOTE: make -j 4 HOSTCC=gcc HOSTCPP=gcc -E zImage CC=arm-poky-linux-gnueabi-gcc -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd ERROR: oe_runmake failed /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 25: arm-poky-linux-gnueabi-gcc: command not found /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 26: arm-poky-linux-gnueabi-gcc: command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 25: arm-poky-linux-gnueabi-gcc: command not found /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 26: arm-poky-linux-gnueabi-gcc: command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found CHK include/config/kernel.release make[2]: arm-poky-linux-gnueabi-gcc: Command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found GEN ./Makefile Using /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source as source for kernel make[2]: arm-poky-linux-gnueabi-gcc: Command not found make[2]: arm-poky-linux-gnueabi-gcc: Command not found HOSTCC scripts/pnmtologo HOSTCC scripts/kallsyms CC scripts/mod/empty.o /bin/sh: 1: arm-poky-linux-gnueabi-gcc: not found /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/Makefile.build:293: recipe for target 'scripts/mod/empty.o' failed make[4]: *** [scripts/mod/empty.o] Error 127 /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/Makefile.build:544: recipe for target 'scripts/mod' failed make[3]: *** [scripts/mod] Error 2 make[3]: *** Waiting for unfinished jobs HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o SHIPPED scripts/dtc/dtc-lexer.lex.c SHIPPED scripts/dtc/dtc-parser.tab.h SHIPPED scripts/dtc/dtc-parser.tab.c HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/dtc /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/Makefile:560: recipe for target 'scripts' failed make[2]: *** [scripts] Error 2 Makefile:150: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 Makefile:24: recipe for target '__sub-make' failed make: *** [__sub-make] Error 2 WARNING: exit code 1 from a shell command. ERROR: Function failed: do_compile (log file is located at /home/mistral/yocto1/poky/build-xfce/tmp/work/odroid_xu3-poky-linux-gnueabi/linux-stable/4.9.13+gitAUTOINC+f3329efb7f-r0/temp/log.do_compile.15577) what is the problem and how to solve this problem ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] core-image-minimal-xfce error
Thank you for your answers.
I checked out the correct branch of meta-openembedded.
Now it is building properly i checked for qemux86 machine, *
core-image-minimal-xfce* image builded and working fine.
Now i am trying to build for odroid-xu3 board.
On Tue, Mar 14, 2017 at 3:35 PM, Burton, Ross <ross.bur...@intel.com> wrote:
>
> On 14 March 2017 at 09:20, ravikiran j <ravikira...@mistralsolutions.com>
> wrote:
>
>>
>> *ERROR: ExpansionError during parsing
>> /home/mistral/yocto/poky/meta-openembedded/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.0.bb
>> <http://xfce4-power-manager_1.6.0.bb>: Failure expanding variable
>> PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
>> 'systemd', d)} which triggered exception AttributeError: 'module' object
>> has no attribute 'filter'*
>
>
> This error message tells me that you're using meta-openembedded master,
> not krogoth. Checkout the correct branch of meta-openembedded.
>
> Ross
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] core-image-minimal-xfce error
Hi everybody,
I am getting some errors in building of *core-image-minimal-xfce *image.
I am using ubuntu 14.04 build system and Yocto 2.1.
I added the meta-openembedded layer into poky and configured the
bblayers.con ffile as follows.
POKY_BBLAYERS_CONF_VERSION = "2"
4
5 BBPATH = "${TOPDIR}"
6 BBFILES ?= ""
7
8 BBLAYERS ?= " \
* 9 /home/mistral/yocto/poky/meta \ 10
/home/mistral/yocto/poky/meta-poky \ 11
/home/mistral/yocto/poky/meta-yocto-bsp \ 12
/home/mistral/yocto/poky/meta-openembedded/meta-oe \ 13
/home/mistral/yocto/poky/meta-openembedded/meta-gnome \ 14
/home/mistral/yocto/poky/meta-openembedded/meta-multimedia \ 15
/home/mistral/yocto/poky/meta-openembedded/meta-python \ 16
/home/mistral/yocto/poky/meta-openembedded/meta-xfce \ 17 "*
i am getting following error after *bitbake*
*core-image-minimal-xfceERROR: ExpansionError during parsing
/home/mistral/yocto/poky/meta-openembedded/meta-xfce/recipes-xfce/xfce4-power-manager/xfce4-power-manager_1.6.0.bb
: Failure expanding variable
PACKAGECONFIG, expression was ${@bb.utils.filter('DISTRO_FEATURES',
'systemd', d)} which triggered exception AttributeError: 'module' object
has no attribute 'filter'*
What is the problem and how to solve this problem ?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Procedure to build the xfce UI for ODROID XU3 board
I cloned the meta-openembedded layer and added inside the poky.
then changed the conf/bblayers.conf as follow.
I found that meta-xfce layer depends on openembedded core, oe , multimedia
, gnome, and python.
so i made the following changes in the bblayers.conf file.
OKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/kamama-yocto/yocto/tmp/poky/meta \
/home/kamama-yocto/yocto/tmp/poky/meta-poky \
/home/kamama-yocto/yocto/tmp/poky/meta-yocto-bsp \
* /home/kamama-yocto/yocto/tmp/poky/meta-odroid \
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-xfce \
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-oe \
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-multimedia \
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-gnome \
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-python \*
"
then i trying to build the
*image core-image-minimal-xfce*
Building gives the following errors.
ERROR: ExpansionError during parsing
/home/kamama-yocto/yocto/tmp/poky/meta-openembedded/meta-python/recipes-extended/python-pyephem/
python-pyephem_3.7.6.0.bb
Traceback (most recent call last):
File "/home/kamama-yocto/yocto/tmp/poky/bitbake/lib/bb/data_smart.py",
line 386, in DataSmart.expandWithRefs(s=' ${PYPI_SRC_URI}',
varname='SRC_URI'):
try:
>s = __expand_var_regexp__.sub(varparse.var_sub, s)
try:
File "/home/kamama-yocto/yocto/tmp/poky/bitbake/lib/bb/data_smart.py",
line 111, in VariableParse.var_sub(match=<_sre.SRE_Match object; span=(1,
16), match='${PYPI_SRC_URI}'>):
else:
>var = self.d.getVarFlag(key, "_content", True)
self.references.add(key)
File "/home/kamama-yocto/yocto/tmp/poky/bitbake/lib/bb/data_smart.py",
line 737, in DataSmart.getVarFlag(var='PYPI_SRC_URI', flag='_content',
expand=True, noweakdefault=False, parsing=False):
cachename = var + "[" + flag + "]"
>value = self.expand(value, cachename)
File "/home/kamama-yocto/yocto/tmp/poky/bitbake/lib/bb/data_smart.py",
line 410, in DataSmart.expand(s='${@pypi_src_uri(d)}',
varname='PYPI_SRC_URI'):
def expand(self, s, varname = None):
>return self.expandWithRefs(s, varname).value
File "/home/kamama-yocto/yocto/tmp/poky/bitbake/lib/bb/data_smart.py",
line 400, in DataSmart.expandWithRefs(s='${@pypi_src_uri(d)}',
varname='PYPI_SRC_URI'):
except Exception as exc:
>raise ExpansionError(varname, s, exc) from exc
bb.data_smart.ExpansionError: Failure expanding variable PYPI_SRC_URI,
expression was ${@pypi_src_uri(d)} which triggered exception TypeError:
getVar() missing 1 required positional argument: 'expand'
how to solve this problems ?
On Mon, Mar 13, 2017 at 7:51 PM, Burton, Ross <ross.bur...@intel.com> wrote:
>
> On 13 March 2017 at 13:54, ravikiran j <ravikira...@mistralsolutions.com>
> wrote:
>
>> What is the procedure to build the xfce UI for ODROID XU3 board.
>>
>
> Add meta-xfce to bblayers.conf, then build an image that contains xfce
> (either add it to your image, or build the sample image
> core-image-minimal-xfce).
>
> Ross
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Procedure to build the xfce UI for ODROID XU3 board
I am able to build the bootloaders, linux kernel (zImage), modules and rootfs images for ODROID XU3 board using Yocto-poky. What is the procedure to build the xfce UI for ODROID XU3 board. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] GUI supported by Yocto project
what are all different GUI supported by the Yocto project ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
