[yocto] beagleboard not booting to SATO interface
Hello This is the first time that I have created and MMC for the beagleboard on a RHELx86_64 6.3. The beagleboard boots and the YOCTO display comes up but never goes to the SATO display. WARNING: Host distribution Red Hat Enterprise Linux Workstation release 6.3 (Santiago) has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Build Configuration: BB_VERSION= 1.17.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = RedHatEnterpriseWorkstation-6.3 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = beagleboard DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20121208 TUNE_FEATURES = armv7a vfp neon TARGET_FPU= vfp-neon meta meta-yocto meta-yocto-bsp= master:c607095894cab60493ddfc4b967b0325e1c313b4 NOTE: recipe core-image-sato-sdk-1.0-r0: task do_rootfs: Succeeded NOTE: Running noexec task 6235 of 6235 (ID: 11, /home/vidal/poky/meta/recipes-sato/images/core-image-sato-sdk.bb, do_build) NOTE: Tasks Summary: Attempted 6235 tasks of which 5220 didn't need to be rerun and all succeeded. The Xorg.log is okay up to the end where the following shows the error. [2058343.877] ABI class: X.Org XInput driver, version 18.0 [2058343.877] (EE) No drivers available. [2058343.877] Fatal server error: [2058343.878] no screens found [2058343.878] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [2058343.879] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [2058343.879] (EE) [2058343.890] Server terminated with error (1). Closing log file. Networking is working Okay. Any help will be welcomed. Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to check if systemd is correctly setup
Hi, I haven't used systemd before, and I've just built a linux kernel image using the latest yocto poky/master. The boot process starts as normal, but it just displays freeing memory (some value) and I get no console prompt. Q1: Which config setting or recipe code, controls the inclusion of systemd in the root filesystem? Q2: How can I check to see if systemd is properly configured for my target (virtex-5-powerpc-405-ml507-softfloat)? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA issue with custom recipe
I am trying to create a simple hello world recipe for a helloworld.c
file. The recipe almost works except it hits a QA issue: WARNING: QA
Issue: hello: Files/directories were installed but not shipped
The warning leads to a failure in the do_rootfs.
WARNING: QA Issue: hello: Files/directories were installed but not
shipped
/usr
/usr/bin
ERROR: Function failed: do_rootfs
--
What am I missing in the recipe?
--
Regards,
Sean D. Liming
Owner
Annabooks
Cell: 858-774-3176
-- next part -- DESCRIPTION = Hello World
Application
LICENSE = GPL-2
LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
SECTION = apps
SRC_URI = file:///home/sean/workspace/Hello/HelloYocto.c
SRC_URI[md5sum] = 4f5c57b446cc08a7299d4dca58c49cda
SRC_URI[sha256sum] =
f357d9214f9c585d8b3997c6a3038eb28b218de264a8bb39ae8474949ad2b98d
S = ${WORKDIR}
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} /home/sean/workspace/Hello/HelloYocto.c -
o
helloyocto }
do_install() {
install -d ${D}${bindir}
install -m 0755 helloyocto ${D}{bindir} }
Sean,
I think you need to note which files are installed by the packages
associated with this recipe, via:
FILES_${PN} = ${bindir}
For more info on these, Check out the FILES and CONFFILES
variables in the Poky Reference Manual. I also found it helpful
to grep around some of the bigger recipes to see how they use
these. (I got a bit tripped up with some libraries with the sonames
set!)
Regards,
Jon
John,
Thank you. The Q/A Warning is gone. That is one step closer, but the
package
is still not resolved.
-
Processing HelloYocto...
Unable to resolve package HelloYocto
ERROR: some packages were missing
ERROR: Function failed: do_rootfs (see
/home/sean/Yocto1.3/n2800/tmp/work/cedartrail-poky-linux/core-image-minimal-
1.0-r0/temp/log.do_rootfs.24265 for further information)
--
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Hi Sean,
What's the name of your hello world recipe? Try naming it hello-world.bb or
hello-world_0.1.0.bb (for a version 0.1.0) and appending hello-world to your
IMAGE_INSTALL.
I believe recipe names must be lower case and use '-' as a separator. An
underscore is used to separate the package name and the version number, as
I've shown above.
It looks like someone posted a great hello world example on the wiki, so be sure
to check that out:
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_my_recipe_into_Yocto.3F
Take a look at meta-skeleton as well. I found that to provide a few very helpful
examples as well. :)
Cheers!
Jon
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to check if systemd is correctly setup
On 2012-12-08 07:19, Elvis Dowson wrote: Hi, I haven't used systemd before, and I've just built a linux kernel image using the latest yocto poky/master. The boot process starts as normal, but it just displays freeing memory (some value) and I get no console prompt. Q1: Which config setting or recipe code, controls the inclusion of systemd in the root filesystem? Q2: How can I check to see if systemd is properly configured for my target (virtex-5-powerpc-405-ml507-softfloat)? First thing, make sure that your kernel has this in the config: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y The latest udev (rev 182) has to have this to work. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA issue with custom recipe
-Original Message-
From: Jon Szymaniak [mailto:jon.szyman...@gmail.com]
Sent: Saturday, December 08, 2012 7:05 AM
To: Sean Liming
Cc: yocto@yoctoproject.org
Subject: Re: QA issue with custom recipe
I am trying to create a simple hello world recipe for a
helloworld.c file. The recipe almost works except it hits a QA
issue: WARNING: QA
Issue: hello: Files/directories were installed but not shipped
The warning leads to a failure in the do_rootfs.
WARNING: QA Issue: hello: Files/directories were installed but not
shipped
/usr
/usr/bin
ERROR: Function failed: do_rootfs
--
What am I missing in the recipe?
--
Regards,
Sean D. Liming
Owner
Annabooks
Cell: 858-774-3176
-- next part -- DESCRIPTION = Hello World
Application
LICENSE = GPL-2
LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
SECTION = apps
SRC_URI = file:///home/sean/workspace/Hello/HelloYocto.c
SRC_URI[md5sum] = 4f5c57b446cc08a7299d4dca58c49cda
SRC_URI[sha256sum] =
f357d9214f9c585d8b3997c6a3038eb28b218de264a8bb39ae8474949ad2b98d
S = ${WORKDIR}
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS}
/home/sean/workspace/Hello/HelloYocto.c -
o
helloyocto }
do_install() {
install -d ${D}${bindir}
install -m 0755 helloyocto ${D}{bindir} }
Sean,
I think you need to note which files are installed by the packages
associated with this recipe, via:
FILES_${PN} = ${bindir}
For more info on these, Check out the FILES and CONFFILES variables
in the Poky Reference Manual. I also found it helpful to grep around
some of the bigger recipes to see how they use these. (I got a bit
tripped up with some libraries with the sonames
set!)
Regards,
Jon
John,
Thank you. The Q/A Warning is gone. That is one step closer, but the
package is still not resolved.
-
Processing HelloYocto...
Unable to resolve package HelloYocto
ERROR: some packages were missing
ERROR: Function failed: do_rootfs (see
/home/sean/Yocto1.3/n2800/tmp/work/cedartrail-poky-linux/core-image-
mi
nimal-
1.0-r0/temp/log.do_rootfs.24265 for further information)
--
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Hi Sean,
What's the name of your hello world recipe? Try naming it hello-world.bb
or
hello-world_0.1.0.bb (for a version 0.1.0) and appending hello-world to
your
IMAGE_INSTALL.
I believe recipe names must be lower case and use '-' as a separator. An
underscore is used to separate the package name and the version number,
as I've shown above.
It looks like someone posted a great hello world example on the wiki, so
be
sure to check that out:
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_my_recip
e_into_Yocto.3F
Take a look at meta-skeleton as well. I found that to provide a few very
helpful examples as well. :)
Cheers!
Jon
Jon,
Good ideas. I tried the wiki how-to again, this time it worked with some
modifications, and I will tweak it to match the title rules. Now, I need to
get my own project working.
Thanks for the help.
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] beagleboard not booting to SATO interface
Hello, Checking I did no have the file /usr/lib/xorg/modules/drivers/omapfb_drv.so only the file /usr/lib/xorg/modules/drivers/omap_drv.so I copied the file /usr/lib/xorg/modules/drivers/omapfb_drv.so from a core-image-sato previous version that was working. Then I get the following in the /var/log/Xorg.0.log [2058242.925] (II) Loading /usr/lib/xorg/modules/drivers/omapfb_drv.so [2058242.931] (II) Module omapfb: vendor=X.Org Foundation [2058242.932] compiled for 1.11.4, module version = 0.1.1 [2058242.932] ABI class: X.Org Video Driver, version 11.0 [2058242.932] (EE) module ABI major version (11) doesn't match the server's version (13) [2058242.932] (II) UnloadModule: omapfb [2058242.932] (II) Unloading omapfb [2058242.933] (EE) Failed to load module omapfb (module requirement mismatch, 0) Any help will be welcomed Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to check if systemd is correctly setup
Hi Gary, Thanks for the reply! On Dec 8, 2012, at 8:02 PM, Gary Thomas g...@mlbassoc.com wrote: On 2012-12-08 07:19, Elvis Dowson wrote: Hi, I haven't used systemd before, and I've just built a linux kernel image using the latest yocto poky/master. The boot process starts as normal, but it just displays freeing memory (some value) and I get no console prompt. Q1: Which config setting or recipe code, controls the inclusion of systemd in the root filesystem? Q2: How can I check to see if systemd is properly configured for my target (virtex-5-powerpc-405-ml507-softfloat)? First thing, make sure that your kernel has this in the config: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y The latest udev (rev 182) has to have this to work. Yes, my defconfig has the above two configs set. Which file control if systemd gets pulled into the core-image-minimal recipe? Where are the systemd configuration files stored? Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to check if systemd is correctly setup
Hi, On Dec 8, 2012, at 8:02 PM, Gary Thomas g...@mlbassoc.com wrote: First thing, make sure that your kernel has this in the config: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y The latest udev (rev 182) has to have this to work. In my kernel boot message, devtmpfs: mounted Freeing unused kernel memory : 168k freed _ I am able to ping to the board from a terminal console on the host, and I get a reply. However, I don't see a console prompt, even though on my bootargs i have set init=/bin/sh Best regards, Elvis Dowson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] bbappending a bbappend
Is it possible to have more than one bbappend applied to a recipe? I'm using meta-cedartrail with my own layer (which is set as lower priority). Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to be able to enable CONFIG_HID_APPLE in my layer so my Apple keyboard works (and keep meta-cedartrail 'clean'). Is it possible to use another linux-yocto_3.0.bbappend in my layer? I've given it a try, but it's not working and I thought it would be an idea to see if it __should__ before I try and fix it ;-) Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappending a bbappend
On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp opensou...@keylevel.com wrote: Is it possible to have more than one bbappend applied to a recipe? I'm using meta-cedartrail with my own layer (which is set as lower priority). Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to be able to enable CONFIG_HID_APPLE in my layer so my Apple keyboard works (and keep meta-cedartrail 'clean'). Is it possible to use another linux-yocto_3.0.bbappend in my layer? I've given it a try, but it's not working and I thought it would be an idea to see if it __should__ before I try and fix it ;-) All bbappends from all layers are applied, in layer priority order. -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappending a bbappend
On 9 Dec 2012, at 00:11, Chris Larson wrote: On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp opensou...@keylevel.com wrote: Is it possible to have more than one bbappend applied to a recipe? I'm using meta-cedartrail with my own layer (which is set as lower priority). Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to be able to enable CONFIG_HID_APPLE in my layer so my Apple keyboard works (and keep meta-cedartrail 'clean'). Is it possible to use another linux-yocto_3.0.bbappend in my layer? I've given it a try, but it's not working and I thought it would be an idea to see if it __should__ before I try and fix it ;-) All bbappends from all layers are applied, in layer priority order. Thanks, I was hoping that was the case. I wonder why this isn't working then - I think I've done it as shown in the dev manual... -- Christopher Larson Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bbappending a bbappend
On Sat, Dec 8, 2012 at 5:54 PM, Chris Tapp opensou...@keylevel.com wrote: On 9 Dec 2012, at 00:11, Chris Larson wrote: On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp opensou...@keylevel.comwrote: Is it possible to have more than one bbappend applied to a recipe? I'm using meta-cedartrail with my own layer (which is set as lower priority). Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to be able to enable CONFIG_HID_APPLE in my layer so my Apple keyboard works (and keep meta-cedartrail 'clean'). Is it possible to use another linux-yocto_3.0.bbappend in my layer? I've given it a try, but it's not working and I thought it would be an idea to see if it __should__ before I try and fix it ;-) All bbappends from all layers are applied, in layer priority order. Thanks, I was hoping that was the case. I wonder why this isn't working then - I think I've done it as shown in the dev manual... Try making use of bitbake-layers show-appends (iirc) -- Christopher Larson ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Package Report System]Upgrade recipes name list
This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-xxx in upstream_tracking files to ignore this recipe remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON_pn-xxx = Not upgrade to 2.0 because the new version is unstable You can check the detail information at http://packages.yoctoproject.org/upgradepkgname PackageName Version UpVersion MaintainerNoUpgradeReason sysprof 1.1.8+git1+4692f85f625f4 1.2.0 Tom Zanussi tom.zanu...@intel.com systemtap-uprobes 1.8+git1+48fa6b5e1d3e636 209.132.183.64 Tom Zanussi tom.zanu...@intel.com shadow4.1.4.3 4.1.5.1 Scott Garman scott.a.gar...@intel.com sudo 1.8.5p2 1.8.6 Scott Garman scott.a.gar...@intel.com blktool 4-6 4 Scott Garman scott.a.gar...@intel.com apmd 3.2.2-14 3.2.2 Scott Garman scott.a.gar...@intel.com openssh 6.0p1 6.1p1 Scott Garman scott.a.gar...@intel.com libtasn1 2.14 3.2 Saul Wold s...@linux.intel.com libnl 3.2.143.2.16 Saul Wold s...@linux.intel.com libnl-3.2.2 is incompatible w... createrepo0.4.110.9.9 Saul Wold s...@linux.intel.com Versions after 0.9.* use YUM,... cmake 2.8.10.1 2.8.10.2 Saul Wold s...@linux.intel.com apt 0.7.140.9.7.6 Saul Wold s...@linux.intel.com pkgconfig 0.25 0.27.1 Saul Wold s...@linux.intel.com removes glib-conf, adds circu... build-appliance-image 1.0 3.2.1 Saul Wold s...@linux.intel.com dhcp 4.2.4-P2 4.2.4 Saul Wold s...@linux.intel.com mtdev 1.1.2 1.1.3 Ross Burton ross.bur...@intel.com logrotate 3.8.1 3.8.3 Robert Yang liezhi.y...@windriver.com iputils s20101006 20121126 Radu Moisan radu.moi...@intel.com ed1.6 1.7 Radu Moisan radu.moi...@intel.com cronie1.4.8 1.4.9 Radu Moisan radu.moi...@intel.com apr-util 1.4.1 1.5.1 Radu Moisan radu.moi...@intel.com liburcu 0.7.4 0.7.5 Radu Moisan radu.moi...@intel.com curl 7.26.07.28.1 Radu Moisan radu.moi...@intel.com js1.7.0+1.8.0rc11.60 Radu Moisan radu.moi...@intel.com u-boot-mkimage2011.06 2012.10 Radu Moisan radu.moi...@intel.com valgrind 3.7.0 3.8.1 Radu Moisan radu.moi...@intel.com babeltrace1.0+git1+f6ed7fa4636ff22 1.0.0 Radu Moisan radu.moi...@intel.com zlib 1.2.7 121 Radu Moisan radu.moi...@intel.com mobile-broadband-provider-info1.0.0+gitr1+d9995ef693cb 20090309 Radu Moisan radu.moi...@intel.com systemtap 1.8+git1+48fa6b5e1d3e636 209.132.183.64 Radu Moisan radu.moi...@intel.com
[yocto] [Package Report System]Manual check recipes name list
This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName Version LastChkVersion LastChkTime Maintainer NoUpgradeReason lsb 4.1 4.1 95 days Yi Zhao yi.z...@windriver.co...No data e2fsprogs1.42.1 1.42.5 103 day Scott Garman scott.a.garman@...No data chrpath 0.140.14104 day Scott Garman scott.a.garman@...No data opensp 1.5.2 1.5.2 100 day Scott Garman scott.a.garman@...No data expat2.1.0 2.0.1 103 day Scott Garman scott.a.garman@...No data nfs-utils1.2.3 1.2.6 100 day Scott Garman scott.a.garman@...No data libpng 1.2.50 1.5.11 157 day Scott Garman scott.a.garman@...1.4.3 and later changes the AP... cracklib 2.8.19 2.8.19 37 days Saul Wold s...@linux.intel.co...No data psmisc 22.20 22.20 37 days Saul Wold s...@linux.intel.co...No data sysstat 10.1.2 10.1.2 37 days Saul Wold s...@linux.intel.co...No data less 456 451 37 days Saul Wold s...@linux.intel.co...No data glew 1.9.0 1.9.0 37 days Saul Wold s...@linux.intel.co...No data libexif 0.6.21 0.6.21 37 days Saul Wold s...@linux.intel.co...No data sqlite3 3.7.14.13.7.14.137 days Saul Wold s...@linux.intel.co...No data boost1.51.0 1.51.0 37 days Saul Wold s...@linux.intel.co...No data libcheck 0.9.9 0.9.9 37 days Saul Wold s...@linux.intel.co...No data kconfig-frontends3.6.0 3.6.0 37 days Saul Wold s...@linux.intel.co...No data sysfsutils 2.1.0 2.1.0 37 days Saul Wold s...@linux.intel.co...No data libcgroup0.37.1 0.38-1 37 days Saul Wold s...@linux.intel.co...No data console-tools0.3.2 0.3.2 37 days Saul Wold s...@linux.intel.co...No data libmad 0.15.1b 0.15.1b 37 days Saul Wold s...@linux.intel.co...No data tzdata 2012d 2012c 94 days Radu Moisan radu.moisan@inte...No data watchdog 5.125.1230 days Radu Moisan radu.moisan@inte...No data hdparm 9.399.3930 days Radu Moisan radu.moisan@inte...No data tslib1.0 1.0 97 days Radu Moisan radu.moisan@inte...No data zip 3.0 3.0 96 days Radu Moisan radu.moisan@inte...No data unzip6.0 6.0 97 days Radu Moisan radu.moisan@inte...No data beecrypt 4.2.1 4.2.1 30 days Radu Moisan radu.moisan@inte...No data setserial
Re: [yocto] bbappending a bbappend
On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp opensou...@keylevel.com wrote: On 9 Dec 2012, at 00:11, Chris Larson wrote: On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp opensou...@keylevel.comwrote: Is it possible to have more than one bbappend applied to a recipe? I'm using meta-cedartrail with my own layer (which is set as lower priority). Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to be able to enable CONFIG_HID_APPLE in my layer so my Apple keyboard works (and keep meta-cedartrail 'clean'). Is it possible to use another linux-yocto_3.0.bbappend in my layer? I've given it a try, but it's not working and I thought it would be an idea to see if it __should__ before I try and fix it ;-) All bbappends from all layers are applied, in layer priority order. Thanks, I was hoping that was the case. I wonder why this isn't working then - I think I've done it as shown in the dev manual... Is it something other than the bbappends ? i.e. are you sure you have all the required dependencies for CONFIG_HID_APPLE already enabled, or in the same fragment you are appending ? Bruce -- Christopher Larson Chris Tapp opensou...@keylevel.com www.keylevel.com ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA issue with custom recipe
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Sean Liming
Sent: Saturday, December 08, 2012 9:22 AM
To: 'Jon Szymaniak'
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] QA issue with custom recipe
-Original Message-
From: Jon Szymaniak [mailto:jon.szyman...@gmail.com]
Sent: Saturday, December 08, 2012 7:05 AM
To: Sean Liming
Cc: yocto@yoctoproject.org
Subject: Re: QA issue with custom recipe
I am trying to create a simple hello world recipe for a
helloworld.c file. The recipe almost works except it hits a QA
issue: WARNING: QA
Issue: hello: Files/directories were installed but not shipped
The warning leads to a failure in the do_rootfs.
WARNING: QA Issue: hello: Files/directories were installed but
not
shipped
/usr
/usr/bin
ERROR: Function failed: do_rootfs
--
What am I missing in the recipe?
--
Regards,
Sean D. Liming
Owner
Annabooks
Cell: 858-774-3176
-- next part -- DESCRIPTION = Hello
World Application
LICENSE = GPL-2
LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58
SECTION = apps
SRC_URI = file:///home/sean/workspace/Hello/HelloYocto.c
SRC_URI[md5sum] = 4f5c57b446cc08a7299d4dca58c49cda
SRC_URI[sha256sum] =
f357d9214f9c585d8b3997c6a3038eb28b218de264a8bb39ae8474949ad2b98d
S = ${WORKDIR}
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS}
/home/sean/workspace/Hello/HelloYocto.c -
o
helloyocto }
do_install() {
install -d ${D}${bindir}
install -m 0755 helloyocto ${D}{bindir} }
Sean,
I think you need to note which files are installed by the packages
associated with this recipe, via:
FILES_${PN} = ${bindir}
For more info on these, Check out the FILES and CONFFILES
variables in the Poky Reference Manual. I also found it helpful to
grep around some of the bigger recipes to see how they use these.
(I got a bit tripped up with some libraries with the sonames
set!)
Regards,
Jon
John,
Thank you. The Q/A Warning is gone. That is one step closer, but the
package is still not resolved.
-
Processing HelloYocto...
Unable to resolve package HelloYocto
ERROR: some packages were missing
ERROR: Function failed: do_rootfs (see
/home/sean/Yocto1.3/n2800/tmp/work/cedartrail-poky-linux/core-
image-
mi
nimal-
1.0-r0/temp/log.do_rootfs.24265 for further information)
--
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Hi Sean,
What's the name of your hello world recipe? Try naming it
hello-world.bb
or
hello-world_0.1.0.bb (for a version 0.1.0) and appending hello-world
to
your
IMAGE_INSTALL.
I believe recipe names must be lower case and use '-' as a separator.
An underscore is used to separate the package name and the version
number, as I've shown above.
It looks like someone posted a great hello world example on the wiki,
so
be
sure to check that out:
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_my_recip
e_into_Yocto.3F
Take a look at meta-skeleton as well. I found that to provide a few
very helpful examples as well. :)
Cheers!
Jon
Jon,
Good ideas. I tried the wiki how-to again, this time it worked with some
modifications, and I will tweak it to match the title rules. Now, I need
to get
my own project working.
Thanks for the help.
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Jon,
Thanks for your help. It was a path problem with the install call. Digging
into the working directory the copy from path needs to be specified.
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA issue with custom recipe
Jon,
Thanks for your help. It was a path problem with the install call. Digging
into the working directory the copy from path needs to be specified.
Regards,
Sean Liming
Owner
Annabooks
Tel: 714-970-7523 / Cell: 858-774-3176
Hi Sean,
Good find! Sorry, I missed that install issue earlier.
Note that if you're only installing a single file, you can make that a
one liner:
do_install() {
install -D -m 0755 ${S}/helloyocto ${D}/{bindir}/helloyocto
}
Best of luck! :)
- Jon
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
