how to copy a tar file to Root file system

how to copy a tar file to Root file system

[Swapna.Gurumani]

[-- Attachment #1.1: Type: text/plain, Size: 1828 bytes --]

Hi, I have a tar file on my local drive and I want to untar this and copy it to my rootfilesystem image.
Please find attached the .bb recipe I am using.
When I run bitbake for this recipe, my build breaks with the following error:
ERROR: crank-1.0-r0 do_install: Function failed: do_install (log file is locate at /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neonpoky-linux-gnueabi/crank/1.0-r0/temp/log.do_install.16738)
ERROR: Logfile of failure stored in: /home/swapna/workspace/work/yocto/poky/buid-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/temp/log.do_intall.16738
Log data follows:
| DEBUG: Executing shell function do_install
| make: *** No rule to make target 'install'.  Stop.
| WARNING: /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5f-neon-poky-linux-gnueabi/crank/1.0-r0/temp/run.do_install.16738:1 exit 2 from make INSTALL_ROOT=/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/crtexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/image install'
| ERROR: Function failed: do_install (log file is located at /home/swapna/worksace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crak/1.0-r0/temp/log.do_install.16738)
ERROR: Task 1095 (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipe-qt/apps/crank_1.0.bb, do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3563 tasks of which 3562 didn't need to be rerunand 1 failed.
No currently running tasks (3056 of 4701)

Summary: 1 task failed:
  /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_.0.bb, do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.



Can someone help me in fixing the .bb recipe?
Regards
Swapna

[-- Attachment #1.2: Type: text/html, Size: 4343 bytes --]

[-- Attachment #2: crank_1.0.bb --]
[-- Type: application/octet-stream, Size: 941 bytes --]

DESCRIPTION = "Crank home automation demo"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690 \
                    file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"

PACKAGES = "${PN}"

PR = "r2"

DEPENDS = "qtbase qtquick1"
inherit qmake5

SRC_URI = "file://crank-V${PV}.tar.gz"

S = "${WORKDIR}/crank-V${PV}"

inherit pkgconfig


FILES_${PN} = " \
  /opt/crank/Home-800/* \
  /opt/crank/Launcher2016_SoftwareRenderer/* \
  /opt/crank/linux-sama5d-armle-fbdev-obj/* \
  /opt/crank/med_demo_2016/* \
  /opt/crank/WashingMachine_V2/* \
  /opt/crank/clear_buffers \
  /opt/crank/layer-enable \
  /opt/crank/README.txt \
  /opt/crank/run_ha.sh \
  /opt/crank/runsb.sh \
  /opt/crank/runsb-480.sh \
  /opt/crank/sb_launch.sh \
  /opt/crank/sbdemo.sh \
  
"


do_install() {
        make INSTALL_ROOT=${D} install
        install -m 0755 ${B}/crank ${D}/opt/crank/


}

Re: how to copy a tar file to Root file system

[Paul Eggleton]

Hi Swapna,

On Tue, 01 Nov 2016 01:17:18 Swapna.Gurumani@microchip.com wrote:
> Hi, I have a tar file on my local drive and I want to untar this and copy it
> to my rootfilesystem image. Please find attached the .bb recipe I am using.
> When I run bitbake for this recipe, my build breaks with the following
> error: ERROR: crank-1.0-r0 do_install: Function failed: do_install (log
> file is locate at
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> poky-linux-gnueabi/crank/1.0-r0/temp/log.do_install.16738) ERROR: Logfile of
> failure stored in:
> /home/swapna/workspace/work/yocto/poky/buid-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r0/temp/log.do_intall.16738
> Log data follows:
> | DEBUG: Executing shell function do_install
> | make: *** No rule to make target 'install'.  Stop.
> | WARNING:
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5f-neo
> | n-poky-linux-gnueabi/crank/1.0-r0/temp/run.do_install.16738:1 exit 2 from
> | make
> | INSTALL_ROOT=/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/
> | crtexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/image install' ERROR:
> | Function failed: do_install (log file is located at
> | /home/swapna/worksace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neo
> | n-poky-linux-gnueabi/crak/1.0-r0/temp/log.do_install.16738)
> ERROR: Task 1095
> (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipe-qt/apps/cran
> k_1.0.bb, do_install) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 3563 tasks of which 3562 didn't need to be rerunand 1 failed. No
> currently running tasks (3056 of 4701)

You say that this is a tarball that you want to untar into the image, but 
inheriting qmake5 and setting DEPENDS suggests that there's more to it than 
that.

As for the failure, it's hard to say without seeing what's been unpacked, but 
perhaps the .pro file in this project doesn't actually have any install 
directives needed to create an install target in the Makefile? If that's the 
case you'll need to install the files "manually" within do_install using 
install and/or cp commands.

A couple of other notes:

* You can simply set FILES_${PN} to "/opt/crank" here, no need to list each 
file unless you have more than one package and you want to split the files 
among them.

* Is this really MIT licensed, or should the LICENSE in fact be "CLOSED"? Then 
you wouldn't need to set LIC_FILES_CHKSUM either. (I'm assuming this is closed 
source software you're packaging).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: how to copy a tar file to Root file system

[Paul Eggleton]

On Tue, 01 Nov 2016 03:12:15 Swapna.Gurumani@microchip.com wrote:
> Thank you so much for your speedy response!!! Actually I ended up attaching
> an older bb file. I had some more modifications as attached. I changed
> license to close per your suggestion. Should I change FILES_${PN} to look
> like this:
> 
> FILES_${PN} = "/opt/crank/"

Yes that would be a lot simpler.

> Actually to be honest I took inspiration from another recipe to make mine.
> All I want to do it take a locally stored .tar.gz file, untar it and put it
> in the /opt folder of my RFS. I notice that the tar file has been extracted
> and I see it in the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r0/crank Folder.
> Do I need a makefile? I don't know what a .po file is..

No, for something simple like this you can do everything you need from the 
recipe.

> How do I install the files "manually" within do_install using install and/or
> cp commands? Like this?:
> 
> do_install() {
>         make INSTALL_ROOT=${D} install    << what does this do>>
>         cp -ar ${B}/crank/ ${D}/opt/
> }
> 

I think you want:

do_install() {
    cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/
}

You don't need the "make install" line.

Cheers,
Paul

PS: please keep the mailing list on CC. Thanks.

Re: how to copy a tar file to Root file system

[Swapna.Gurumani]

[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]

With the attached recipe I get the following error:
ERROR: crank-1.0-r0 do_package: QA Issue: crank: Files/directories were installed but not shipped in any package:
  /opt
  /opt/sb_launch.sh
  /opt/clear_buffers
  /opt/runsb.sh
  /opt/README.txt

......
...
.
.
.

  /opt/WashingMachine_V2/fonts/Roboto-Regular.ttf
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
crank: 1733 installed and not shipped files. [installed-vs-shipped]
ERROR: crank-1.0-r0 do_package: Fatal QA errors found, failing task.
ERROR: crank-1.0-r0 do_package: Function failed: do_package
ERROR: Logfile of failure stored in: /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/temp/log.do_package.19127
ERROR: Task 1104 (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb, do_package) failed with exit code '1'


I feel am very close!! 
Regards
Swapna


-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com] 
Sent: Monday, October 31, 2016 8:35 PM
To: Swapna Gurumani - C40450 <Swapna.Gurumani@microchip.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] how to copy a tar file to Root file system

On Tue, 01 Nov 2016 03:12:15 Swapna.Gurumani@microchip.com wrote:
> Thank you so much for your speedy response!!! Actually I ended up 
> attaching an older bb file. I had some more modifications as attached. 
> I changed license to close per your suggestion. Should I change 
> FILES_${PN} to look like this:
> 
> FILES_${PN} = "/opt/crank/"

Yes that would be a lot simpler.

> Actually to be honest I took inspiration from another recipe to make mine.
> All I want to do it take a locally stored .tar.gz file, untar it and 
> put it in the /opt folder of my RFS. I notice that the tar file has 
> been extracted and I see it in the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf
> -neon- poky-linux-gnueabi/crank/1.0-r0/crank Folder.
> Do I need a makefile? I don't know what a .po file is..

No, for something simple like this you can do everything you need from the recipe.

> How do I install the files "manually" within do_install using install 
> and/or cp commands? Like this?:
> 
> do_install() {
>         make INSTALL_ROOT=${D} install    << what does this do>>
>         cp -ar ${B}/crank/ ${D}/opt/
> }
> 

I think you want:

do_install() {
    cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/ }

You don't need the "make install" line.

Cheers,
Paul

PS: please keep the mailing list on CC. Thanks.



[-- Attachment #2: crank_1.0.bb --]
[-- Type: application/octet-stream, Size: 268 bytes --]

DESCRIPTION = "Crank home automation demo"
LICENSE = "CLOSED"
PACKAGES = "${PN}"

PR = "r0"

SRC_URI = "file://crank-V${PV}.tar.gz"

inherit pkgconfig

FILES_${PN} = "/op/crank/*"


do_install() {
        cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/ 
}

Re: how to copy a tar file to Root file system

[Paul Eggleton]

On Tue, 01 Nov 2016 04:03:58 Swapna.Gurumani@microchip.com wrote:
> With the attached recipe I get the following error:
> ERROR: crank-1.0-r0 do_package: QA Issue: crank: Files/directories were
> installed but not shipped in any package: /opt
>   /opt/sb_launch.sh
>   /opt/clear_buffers
>   /opt/runsb.sh
>   /opt/README.txt

Ah, I think you need this line first in do_install:

    install -d ${D}/opt/crank

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: how to copy a tar file to Root file system

[Bas Mevissen]

On 01/11/16 05:03, Swapna.Gurumani@microchip.com wrote:
> With the attached recipe I get the following error:

 From the recipe:

> inherit pkgconfig

Why do you inherit pkgconfig and aren't you inheriting bin_package?


Regards,

Bas.
-- 
Bas.

Re: how to copy a tar file to Root file system

[Swapna.Gurumani]

[-- Attachment #1: Type: text/plain, Size: 3357 bytes --]

Hello,
Every step I take close, I take 2 back :(
My bb now looks like the one attached. I had to add each folder for FILES_${PN} contrary to your advice otherwise I got the following error:
ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were installed but not shipped in any package:
  /opt
  /opt/crank
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
crank: 2 installed and not shipped files. [installed-vs-shipped]



I am now getting the following error:
ERROR: crank-1.0-r2 do_install: Function failed: do_install (log file is located at /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
ERROR: Logfile of failure stored in: /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457
Log data follows:
| DEBUG: Executing shell function do_install
| cp: cannot stat '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/crank': No such file or directory
| WARNING: /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/temp/run.do_install.26457:1 exit 1 from 'cp -a --no-preserve=ownership /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/crank /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/image/opt/'
| ERROR: Function failed: do_install (log file is located at /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
ERROR: Task 1082 (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb, do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3806 tasks of which 3805 didn't need to be rerun and 1 failed.
No currently running tasks (3034 of 4662)

Summary: 1 task failed:
  /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb, do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.



Also if I look into the 
/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r2
It is empty.
Could you please help me with this?
Regards
Swapna



-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com] 
Sent: Monday, October 31, 2016 11:59 PM
To: Swapna Gurumani - C40450 <Swapna.Gurumani@microchip.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] how to copy a tar file to Root file system

On Tue, 01 Nov 2016 04:03:58 Swapna.Gurumani@microchip.com wrote:
> With the attached recipe I get the following error:
> ERROR: crank-1.0-r0 do_package: QA Issue: crank: Files/directories 
> were installed but not shipped in any package: /opt
>   /opt/sb_launch.sh
>   /opt/clear_buffers
>   /opt/runsb.sh
>   /opt/README.txt

Ah, I think you need this line first in do_install:

    install -d ${D}/opt/crank

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

[-- Attachment #2: crank_1.0.bb --]
[-- Type: application/octet-stream, Size: 935 bytes --]

DESCRIPTION = "Crank home automation demo"
LICENSE = "CLOSED"

PACKAGES = "${PN}"

PR = "r2"
DEPENDS = "tslib alsa-lib"
SRC_URI = "file://crank-v${PV}.tar.gz"

S = "${WORKDIR}/crank-v${PV}"

inherit pkgconfig

FILES_${PN} = " \
  /opt/crank/Home-800/* \
  /opt/crank/Home-800/.* \
  /opt/crank/Launcher2016_SoftwareRenderer/* \
  /opt/crank/Launcher2016_SoftwareRenderer/.* \
  /opt/crank/linux-sama5d-armle-fbdev-obj/* \
  /opt/crank/med_demo_2016/* \
  /opt/crank/med_demo_2016/.* \
  /opt/crank/WashingMachine_V2/* \
  /opt/crank/WashingMachine_V2/.* \
  /opt/crank/clear_buffers \
  /opt/crank/layer-enable \
  /opt/crank/README.txt \
  /opt/crank/run_ha.sh \
  /opt/crank/runsb.sh \
  /opt/crank/runsb-480.sh \
  /opt/crank/sb_launch.sh \
  /opt/crank/sbdemo.sh \
"
do_install() {
     install -d ${D}/opt/crank
     cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/
     install -m 0755 ${WORKDIR}/crank ${D}/opt/crank/
}

Re: how to copy a tar file to Root file system

[Paul Eggleton]

On Tue, 01 Nov 2016 18:45:02 Swapna.Gurumani@microchip.com wrote:
> Every step I take close, I take 2 back :(
> My bb now looks like the one attached. I had to add each folder for
> FILES_${PN} contrary to your advice otherwise I got the following error:
> ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were
> installed but not shipped in any package: /opt
>   /opt/crank
> Please set FILES such that these items are packaged. Alternatively if they
> are unneeded, avoid installing them or delete them within do_install.
> crank: 2 installed and not shipped files. [installed-vs-shipped]
> 
> 
> 
> I am now getting the following error:
> ERROR: crank-1.0-r2 do_install: Function failed: do_install (log file is
> located at
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457) ERROR: Logfile
> of failure stored in:
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457
> Log data follows:
> | DEBUG: Executing shell function do_install
> | cp: cannot stat
> | '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-n
> | eon-poky-linux-gnueabi/crank/1.0-r2/crank': No such file or directory
> | WARNING:
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/run.do_install.26457:1 exit 1 from
> | 'cp -a --no-preserve=ownership
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/crank
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/image/opt/' ERROR: Function failed:
> | do_install (log file is located at
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
> ERROR: Task 1082
> (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cra
> nk_1.0.bb, do_install) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 3806 tasks of which 3805 didn't need to be rerun and 1 failed. No
> currently running tasks (3034 of 4662)
> 
> Summary: 1 task failed:
>  
> /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cran
> k_1.0.bb, do_install Summary: There was 1 WARNING message shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> 
> 
> 
> Also if I look into the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r2 It is empty.

There's something strange going on here, because the path you have just given 
is ${WORKDIR} - and that shouldn't be able to be empty at this point. If 
nothing else there should be a "temp" directory under it containing logs if 
*any* tasks have run. Surely you have skipped out some steps between when it 
was working and now? I notice the tarball name changed - did you regenerate it 
or just rename it?

In any case, when debugging situations like this it helps to make a fresh 
start - run "bitbake -c clean crank" (you don't need -c cleansstate because 
being stuck at do_install you haven't got to any real sstate tasks yet). Then 
methodically run through each task - when do_unpack ran what got unpacked into 
${WORKDIR}? If that's as expected, what got put into ${D} (which is the 
"image" subdirectory under ${WORKDIR})? Does what's in ${D} match up with the 
layout you expect to be on the target? At any time you can use 
"bitbake -e crank | less" to inspect the value of variables. You can also see 
exactly what commands got run within the task by looking at the run.do_* files 
under "temp" in the workdir.

Also:

* That third line "install -m ..." you now have in do_install won't work and 
in any case isn't necessary since you are already copying that with the cp 
command.

* Based on what you've said earlier, your S value cannot be correct - it may 
not matter, but it might as well be fixed anyway. If the tarball unpacks a 
"crank" subdirectory then it should be set to "${WORKDIR}/crank".

* There's no need to set the PR value, in fact doing so only serves to keep 
changing ${WORKDIR} which will potentially get in the way of debugging, so I'd 
suggest not doing that.

* Setting DEPENDS isn't really doing you any good - DEPENDS is for build-time 
dependencies. You're only unpacking a tarball, you don't need any build-time 
dependencies to speak of. If you have runtime dependencies then set them in 
RDEPENDS_${PN} since that's where runtime dependencies need to be set.

* As another responder pointed out, the inherit of pkgconfig isn't needed - 
you don't need pkg-config for anything being done here.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: how to copy a tar file to Root file system

[Daniel.]

[-- Attachment #1: Type: text/plain, Size: 5785 bytes --]

I have an example of a recipe exploding a tar here:
https://gist.github.com/gkos/02eccb8e1e02312327aa6db6cdc9d501
The tar is used as a source. So the bitbake explodes it to ${WORKDIR} and I
simply copy it to /opt
I hope that this helps :)

Regards,

2016-11-01 18:00 GMT-02:00 Paul Eggleton <paul.eggleton@linux.intel.com>:

> On Tue, 01 Nov 2016 18:45:02 Swapna.Gurumani@microchip.com wrote:
> > Every step I take close, I take 2 back :(
> > My bb now looks like the one attached. I had to add each folder for
> > FILES_${PN} contrary to your advice otherwise I got the following error:
> > ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were
> > installed but not shipped in any package: /opt
> >   /opt/crank
> > Please set FILES such that these items are packaged. Alternatively if
> they
> > are unneeded, avoid installing them or delete them within do_install.
> > crank: 2 installed and not shipped files. [installed-vs-shipped]
> >
> >
> >
> > I am now getting the following error:
> > ERROR: crank-1.0-r2 do_install: Function failed: do_install (log file is
> > located at
> > /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-neon
> > -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457) ERROR:
> Logfile
> > of failure stored in:
> > /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-neon
> > -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457
> > Log data follows:
> > | DEBUG: Executing shell function do_install
> > | cp: cannot stat
> > | '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-n
> > | eon-poky-linux-gnueabi/crank/1.0-r2/crank': No such file or directory
> > | WARNING:
> > | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-ne
> > | on-poky-linux-gnueabi/crank/1.0-r2/temp/run.do_install.26457:1 exit 1
> from
> > | 'cp -a --no-preserve=ownership
> > | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-ne
> > | on-poky-linux-gnueabi/crank/1.0-r2/crank
> > | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-ne
> > | on-poky-linux-gnueabi/crank/1.0-r2/image/opt/' ERROR: Function failed:
> > | do_install (log file is located at
> > | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-ne
> > | on-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
> > ERROR: Task 1082
> > (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/
> recipes-qt/apps/cra
> > nk_1.0.bb, do_install) failed with exit code '1' NOTE: Tasks Summary:
> > Attempted 3806 tasks of which 3805 didn't need to be rerun and 1 failed.
> No
> > currently running tasks (3034 of 4662)
> >
> > Summary: 1 task failed:
> >
> > /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/
> recipes-qt/apps/cran
> > k_1.0.bb, do_install Summary: There was 1 WARNING message shown.
> > Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> >
> >
> >
> > Also if I look into the
> > /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/
> work/cortexa5hf-neon-
> > poky-linux-gnueabi/crank/1.0-r2 It is empty.
>
> There's something strange going on here, because the path you have just
> given
> is ${WORKDIR} - and that shouldn't be able to be empty at this point. If
> nothing else there should be a "temp" directory under it containing logs if
> *any* tasks have run. Surely you have skipped out some steps between when
> it
> was working and now? I notice the tarball name changed - did you
> regenerate it
> or just rename it?
>
> In any case, when debugging situations like this it helps to make a fresh
> start - run "bitbake -c clean crank" (you don't need -c cleansstate because
> being stuck at do_install you haven't got to any real sstate tasks yet).
> Then
> methodically run through each task - when do_unpack ran what got unpacked
> into
> ${WORKDIR}? If that's as expected, what got put into ${D} (which is the
> "image" subdirectory under ${WORKDIR})? Does what's in ${D} match up with
> the
> layout you expect to be on the target? At any time you can use
> "bitbake -e crank | less" to inspect the value of variables. You can also
> see
> exactly what commands got run within the task by looking at the run.do_*
> files
> under "temp" in the workdir.
>
> Also:
>
> * That third line "install -m ..." you now have in do_install won't work
> and
> in any case isn't necessary since you are already copying that with the cp
> command.
>
> * Based on what you've said earlier, your S value cannot be correct - it
> may
> not matter, but it might as well be fixed anyway. If the tarball unpacks a
> "crank" subdirectory then it should be set to "${WORKDIR}/crank".
>
> * There's no need to set the PR value, in fact doing so only serves to keep
> changing ${WORKDIR} which will potentially get in the way of debugging, so
> I'd
> suggest not doing that.
>
> * Setting DEPENDS isn't really doing you any good - DEPENDS is for
> build-time
> dependencies. You're only unpacking a tarball, you don't need any
> build-time
> dependencies to speak of. If you have runtime dependencies then set them in
> RDEPENDS_${PN} since that's where runtime dependencies need to be set.
>
> * As another responder pointed out, the inherit of pkgconfig isn't needed -
> you don't need pkg-config for anything being done here.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
*"Do or do not. There is no try"*
  *Yoda Master*

[-- Attachment #2: Type: text/html, Size: 7453 bytes --]

Re: how to copy a tar file to Root file system

[Swapna.Gurumani]

[-- Attachment #1.1: Type: text/plain, Size: 6137 bytes --]

Hi Danile,
Thank you so much for your help. My .bb file now looks like as attached. Did your tar file have .a and .so?? I am getting errors because of them. Can I force the do_package_qa to skip?
Thanks,
Regards
Swapna

From: Daniel. [mailto:danielhilst@gmail.com]
Sent: Tuesday, November 01, 2016 1:18 PM
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Swapna Gurumani - C40450 <Swapna.Gurumani@microchip.com>; yocto@yoctoproject.org
Subject: Re: [yocto] how to copy a tar file to Root file system

I have an example of a recipe exploding a tar here: https://gist.github.com/gkos/02eccb8e1e02312327aa6db6cdc9d501
The tar is used as a source. So the bitbake explodes it to ${WORKDIR} and I simply copy it to /opt
I hope that this helps :)
Regards,

2016-11-01 18:00 GMT-02:00 Paul Eggleton <paul.eggleton@linux.intel.com<mailto:paul.eggleton@linux.intel.com>>:
On Tue, 01 Nov 2016 18:45:02 Swapna.Gurumani@microchip.com<mailto:Swapna.Gurumani@microchip.com> wrote:
> Every step I take close, I take 2 back :(
> My bb now looks like the one attached. I had to add each folder for
> FILES_${PN} contrary to your advice otherwise I got the following error:
> ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were
> installed but not shipped in any package: /opt
>   /opt/crank
> Please set FILES such that these items are packaged. Alternatively if they
> are unneeded, avoid installing them or delete them within do_install.
> crank: 2 installed and not shipped files. [installed-vs-shipped]
>
>
>
> I am now getting the following error:
> ERROR: crank-1.0-r2 do_install: Function failed: do_install (log file is
> located at
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457) ERROR: Logfile
> of failure stored in:
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457
> Log data follows:
> | DEBUG: Executing shell function do_install
> | cp: cannot stat
> | '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-n
> | eon-poky-linux-gnueabi/crank/1.0-r2/crank': No such file or directory
> | WARNING:
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/run.do_install.26457:1 exit 1 from
> | 'cp -a --no-preserve=ownership
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/crank
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/image/opt/' ERROR: Function failed:
> | do_install (log file is located at
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
> ERROR: Task 1082
> (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cra
> nk_1.0.bb<http://nk_1.0.bb>, do_install) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 3806 tasks of which 3805 didn't need to be rerun and 1 failed. No
> currently running tasks (3034 of 4662)
>
> Summary: 1 task failed:
>
> /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cran
> k_1.0.bb<http://k_1.0.bb>, do_install Summary: There was 1 WARNING message shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
>
> Also if I look into the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r2 It is empty.

There's something strange going on here, because the path you have just given
is ${WORKDIR} - and that shouldn't be able to be empty at this point. If
nothing else there should be a "temp" directory under it containing logs if
*any* tasks have run. Surely you have skipped out some steps between when it
was working and now? I notice the tarball name changed - did you regenerate it
or just rename it?

In any case, when debugging situations like this it helps to make a fresh
start - run "bitbake -c clean crank" (you don't need -c cleansstate because
being stuck at do_install you haven't got to any real sstate tasks yet). Then
methodically run through each task - when do_unpack ran what got unpacked into
${WORKDIR}? If that's as expected, what got put into ${D} (which is the
"image" subdirectory under ${WORKDIR})? Does what's in ${D} match up with the
layout you expect to be on the target? At any time you can use
"bitbake -e crank | less" to inspect the value of variables. You can also see
exactly what commands got run within the task by looking at the run.do_* files
under "temp" in the workdir.

Also:

* That third line "install -m ..." you now have in do_install won't work and
in any case isn't necessary since you are already copying that with the cp
command.

* Based on what you've said earlier, your S value cannot be correct - it may
not matter, but it might as well be fixed anyway. If the tarball unpacks a
"crank" subdirectory then it should be set to "${WORKDIR}/crank".

* There's no need to set the PR value, in fact doing so only serves to keep
changing ${WORKDIR} which will potentially get in the way of debugging, so I'd
suggest not doing that.

* Setting DEPENDS isn't really doing you any good - DEPENDS is for build-time
dependencies. You're only unpacking a tarball, you don't need any build-time
dependencies to speak of. If you have runtime dependencies then set them in
RDEPENDS_${PN} since that's where runtime dependencies need to be set.

* As another responder pointed out, the inherit of pkgconfig isn't needed -
you don't need pkg-config for anything being done here.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto



--
"Do or do not. There is no try"
  Yoda Master

[-- Attachment #1.2: Type: text/html, Size: 10767 bytes --]

[-- Attachment #2: crank_1.0.bb --]
[-- Type: application/octet-stream, Size: 937 bytes --]

DESCRIPTION = "Crank home automation demo"
LICENSE = "CLOSED"
TARFILE = "crank-v1.0.tar.gz"
DEPENDS = "tslib alsa-lib"
SRC_URI = "file://${TARFILE}"


INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
S = "${WORKDIR}/crank-v${PV}"

FILES_${PN} = " \
  /opt/crank/Home-800/* \
  /opt/crank/Home-800/.* \
  /opt/crank/Launcher2016_SoftwareRenderer/* \
  /opt/crank/Launcher2016_SoftwareRenderer/.* \
  /opt/crank/linux-sama5d-armle-fbdev-obj/* \
  /opt/crank/linux-sama5d-armle-fbdev-obj/lib/*.a \
  /opt/crank/med_demo_2016/* \
  /opt/crank/med_demo_2016/.* \
  /opt/crank/WashingMachine_V2/* \
  /opt/crank/WashingMachine_V2/.* \
  /opt/crank/clear_buffers \
  /opt/crank/layer-enable \
  /opt/crank/README.txt \
  /opt/crank/run_ha.sh \
  /opt/crank/runsb.sh \
  /opt/crank/runsb-480.sh \
  /opt/crank/sb_launch.sh \
  /opt/crank/sbdemo.sh \
"
do_install() {
     install -d ${D}/opt
     cp -a --no-preserve=ownership ${WORKDIR}/crank ${D}/opt/
}





[-- Attachment #3: error.txt --]
[-- Type: text/plain, Size: 11496 bytes --]

WARNING: crank-1.0-r0 do_package_qa: QA Issue: ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/sbio_tcprelay.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/lgre.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/luagretest.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/gredom.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsblua.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libgre.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsbexternal.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-system.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-tslib.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-selftest.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-timer.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-poly.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-gesture.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-screen-dump-test.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/librender-plugin-fbdev.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-screen-path.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-event-redirect.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-dynamic-rext.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-media.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-lua.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-screen-dump.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-rext-external.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-mtdev.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-dev-input.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-audio.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-browser.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-screen-scale.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-capture-playback.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-greio.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-circle.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-animation.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/plugins/libgre-plugin-logger.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lua/luasocket/linux-armle/mime/core.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lua/luasocket/linux-armle/socket/core.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lua/lfs/linux-armle/lfs.so' has relocations in .text
ELF binary '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lua/luasql/linux-armle/luasql_sqlite3.so' has relocations in .text [textrel]
ERROR: crank-1.0-r0 do_package_qa: QA Issue: non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libscene3d.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libswrender.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libgretest.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsbimage.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsqlite3.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libgreio.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libgreal.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsbfont.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libsbfreetype.a'
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libssgf.a' [staticdev]
ERROR: crank-1.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: crank-1.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/temp/log.do_package_qa.10609
ERROR: Task 9 (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb, do_package_qa) failed with exit code '1'
NOTE: Tasks Summary: Attempted 396 tasks of which 385 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/crank_1.0.bb, do_package_qa
Summary: There were 2 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

Re: how to copy a tar file to Root file system

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

On 2 November 2016 at 20:00, <Swapna.Gurumani@microchip.com> wrote:

> Thank you so much for your help. My .bb file now looks like as attached.
> Did your tar file have .a and .so?? I am getting errors because of them.
> Can I force the do_package_qa to skip?
>
>
You might find this document useful:
https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries

Ross

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

Re: how to copy a tar file to Root file system

[Swapna.Gurumani]

> 
> Also if I look into the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf
> -neon-
> poky-linux-gnueabi/crank/1.0-r2 It is empty.

There's something strange going on here, because the path you have just given is ${WORKDIR} - and that shouldn't be able to be empty at this point. If nothing else there should be a "temp" directory under it containing logs if
*any* tasks have run. Surely you have skipped out some steps between when it was working and now? I notice the tarball name changed - did you regenerate it or just rename it?

Answer>> I renamed it. For some reason it was. But now its populated with lot of stuff including the crank folder, temp, image etc..


In any case, when debugging situations like this it helps to make a fresh start - run "bitbake -c clean crank" (you don't need -c cleansstate because being stuck at do_install you haven't got to any real sstate tasks yet). Then methodically run through each task - when do_unpack ran what got unpacked into ${WORKDIR}? If that's as expected, what got put into ${D} (which is the "image" subdirectory under ${WORKDIR})? Does what's in ${D} match up with the layout you expect to be on the target? At any time you can use "bitbake -e crank | less" to inspect the value of variables. You can also see exactly what commands got run within the task by looking at the run.do_* files under "temp" in the workdir.
 
ANSWER >> All this looks good. The run.do* files don't show much. Although, why am I seeing stuff like:
NOTE: arm-poky-linux-gnueabi-objdump -p /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/luagretest.so

In log.do_package_qa?


* Based on what you've said earlier, your S value cannot be correct - it may not matter, but it might as well be fixed anyway. If the tarball unpacks a "crank" subdirectory then it should be set to "${WORKDIR}/crank".

ANSWER >> I get the same error no matter what the S is set to:
non -staticdev package contains static .a library: crank path 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d-armle-fbdev-obj/lib/libssgf.a' [staticdev]


WHY am I getting this error?


* Setting DEPENDS isn't really doing you any good - DEPENDS is for build-time dependencies. You're only unpacking a tarball, you don't need any build-time dependencies to speak of. If you have runtime dependencies then set them in RDEPENDS_${PN} since that's where runtime dependencies need to be set.

ANSWER>> without that line, I get the following error:

WARNING: crank-1.0-r0 do_package_qa: QA Issue: crank rdepends on tslib, but it isn't a build dependency, missing tslib in DEPENDS or PACKAGECONFIG? [build-deps]
WARNING: crank-1.0-r0 do_package_qa: QA Issue: crank rdepends on libasound, but it isn't a build dependency, missing alsa-lib in DEPENDS or PACKAGECONFIG? [build-deps]


* As another responder pointed out, the inherit of pkgconfig isn't needed - you don't need pkg-config for anything being done here.
Again, same error with or without this. Or even if I use " inherit bin_package"



Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: how to copy a tar file to Root file system

[Swapna.Gurumani]

[-- Attachment #1: Type: text/plain, Size: 6228 bytes --]

Thank you to Paul Eggleton, Daniel and Ross Burton.
I was able to solve by miseries by adding the following line to my miseries:

FILES_${PN}-staticdev = "/opt/crank/linux-sama5d-armle-fbdev-obj/lib/*.a"

Ref:
http://stackoverflow.com/questions/28792597/how-to-add-a-new-library-using-yocto
Regards

Swapna
From: Daniel. [mailto:danielhilst@gmail.com]
Sent: Tuesday, November 01, 2016 1:18 PM
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Swapna Gurumani - C40450 <Swapna.Gurumani@microchip.com>; yocto@yoctoproject.org
Subject: Re: [yocto] how to copy a tar file to Root file system

I have an example of a recipe exploding a tar here: https://gist.github.com/gkos/02eccb8e1e02312327aa6db6cdc9d501
The tar is used as a source. So the bitbake explodes it to ${WORKDIR} and I simply copy it to /opt
I hope that this helps :)
Regards,

2016-11-01 18:00 GMT-02:00 Paul Eggleton <paul.eggleton@linux.intel.com<mailto:paul.eggleton@linux.intel.com>>:
On Tue, 01 Nov 2016 18:45:02 Swapna.Gurumani@microchip.com<mailto:Swapna.Gurumani@microchip.com> wrote:
> Every step I take close, I take 2 back :(
> My bb now looks like the one attached. I had to add each folder for
> FILES_${PN} contrary to your advice otherwise I got the following error:
> ERROR: crank-1.0-r2 do_package: QA Issue: crank: Files/directories were
> installed but not shipped in any package: /opt
>   /opt/crank
> Please set FILES such that these items are packaged. Alternatively if they
> are unneeded, avoid installing them or delete them within do_install.
> crank: 2 installed and not shipped files. [installed-vs-shipped]
>
>
>
> I am now getting the following error:
> ERROR: crank-1.0-r2 do_install: Function failed: do_install (log file is
> located at
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457) ERROR: Logfile
> of failure stored in:
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457
> Log data follows:
> | DEBUG: Executing shell function do_install
> | cp: cannot stat
> | '/home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-n
> | eon-poky-linux-gnueabi/crank/1.0-r2/crank': No such file or directory
> | WARNING:
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/run.do_install.26457:1 exit 1 from
> | 'cp -a --no-preserve=ownership
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/crank
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/image/opt/' ERROR: Function failed:
> | do_install (log file is located at
> | /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-ne
> | on-poky-linux-gnueabi/crank/1.0-r2/temp/log.do_install.26457)
> ERROR: Task 1082
> (/home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cra
> nk_1.0.bb<http://nk_1.0.bb>, do_install) failed with exit code '1' NOTE: Tasks Summary:
> Attempted 3806 tasks of which 3805 didn't need to be rerun and 1 failed. No
> currently running tasks (3034 of 4662)
>
> Summary: 1 task failed:
>
> /home/swapna/workspace/work/yocto/meta-atmel/qt5-layer/recipes-qt/apps/cran
> k_1.0.bb<http://k_1.0.bb>, do_install Summary: There was 1 WARNING message shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
>
> Also if I look into the
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon-
> poky-linux-gnueabi/crank/1.0-r2 It is empty.

There's something strange going on here, because the path you have just given
is ${WORKDIR} - and that shouldn't be able to be empty at this point. If
nothing else there should be a "temp" directory under it containing logs if
*any* tasks have run. Surely you have skipped out some steps between when it
was working and now? I notice the tarball name changed - did you regenerate it
or just rename it?

In any case, when debugging situations like this it helps to make a fresh
start - run "bitbake -c clean crank" (you don't need -c cleansstate because
being stuck at do_install you haven't got to any real sstate tasks yet). Then
methodically run through each task - when do_unpack ran what got unpacked into
${WORKDIR}? If that's as expected, what got put into ${D} (which is the
"image" subdirectory under ${WORKDIR})? Does what's in ${D} match up with the
layout you expect to be on the target? At any time you can use
"bitbake -e crank | less" to inspect the value of variables. You can also see
exactly what commands got run within the task by looking at the run.do_* files
under "temp" in the workdir.

Also:

* That third line "install -m ..." you now have in do_install won't work and
in any case isn't necessary since you are already copying that with the cp
command.

* Based on what you've said earlier, your S value cannot be correct - it may
not matter, but it might as well be fixed anyway. If the tarball unpacks a
"crank" subdirectory then it should be set to "${WORKDIR}/crank".

* There's no need to set the PR value, in fact doing so only serves to keep
changing ${WORKDIR} which will potentially get in the way of debugging, so I'd
suggest not doing that.

* Setting DEPENDS isn't really doing you any good - DEPENDS is for build-time
dependencies. You're only unpacking a tarball, you don't need any build-time
dependencies to speak of. If you have runtime dependencies then set them in
RDEPENDS_${PN} since that's where runtime dependencies need to be set.

* As another responder pointed out, the inherit of pkgconfig isn't needed -
you don't need pkg-config for anything being done here.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto



--
"Do or do not. There is no try"
  Yoda Master

[-- Attachment #2: Type: text/html, Size: 11344 bytes --]

Re: how to copy a tar file to Root file system

[Paul Eggleton]

On Wed, 02 Nov 2016 20:17:11 Swapna.Gurumani@microchip.com wrote:
> > In any case, when debugging situations like this it helps to make a fresh
> > start - run "bitbake -c clean crank" (you don't need -c cleansstate
> > because being stuck at do_install you haven't got to any real sstate tasks
> > yet). Then methodically run through each task - when do_unpack ran what
> > got unpacked into ${WORKDIR}? If that's as expected, what got put into
> > ${D} (which is the "image" subdirectory under ${WORKDIR})? Does what's in
> > ${D} match up with the layout you expect to be on the target? At any time
> > you can use "bitbake -e crank | less" to inspect the value of variables.
> > You can also see exactly what commands got run within the task by looking
> > at the run.do_* files under "temp" in the workdir.
>
> ANSWER >> All this looks good. The run.do* files don't show much. Although,
> why am I seeing stuff like: NOTE: arm-poky-linux-gnueabi-objdump -p
> /home/swapna/workspace/work/yocto/poky/build-atmel/tmp/work/cortexa5hf-neon
> -poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/opt/crank/linux-sama5d
> -armle-fbdev-obj/lib/luagretest.so In log.do_package_qa?

There are various QA checks on the output (as you've no doubt seen) - some of
those require examining binaries such as the checks on rpaths, and that
requires running objdump.

> > * Based on what you've said earlier, your S value cannot be correct - it
> > may not matter, but it might as well be fixed anyway. If the tarball
> > unpacks a "crank" subdirectory then it should be set to
> > "${WORKDIR}/crank".
> 
> ANSWER >> I get the same error no matter what the S is set to:
> non -staticdev package contains static .a library: crank path
> 'work/cortexa5hf-neon-poky-linux-gnueabi/crank/1.0-r0/packages-split/crank/
> opt/crank/linux-sama5d-armle-fbdev-obj/lib/libssgf.a' [staticdev]
> 
> WHY am I getting this error?

That error has nothing to do with the S value - as I mentioned, S may not
matter in this case, but it might as well be correct if you're setting it at
all.

You resolved this issue in the end, but for future reference there is a guide
on how to deal with various QA errors/warnings here:

http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-errors-and-warnings
 
> > * Setting DEPENDS isn't really doing you any good - DEPENDS is for
> > build-time dependencies. You're only unpacking a tarball, you don't need
> > any build-time dependencies to speak of. If you have runtime dependencies
> > then set them in RDEPENDS_${PN} since that's where runtime dependencies
> > need to be set.
>
> ANSWER>> without that line, I get the following error:
> 
> WARNING: crank-1.0-r0 do_package_qa: QA Issue: crank rdepends on tslib, but
> it isn't a build dependency, missing tslib in DEPENDS or PACKAGECONFIG?
> [build-deps] 
> WARNING: crank-1.0-r0 do_package_qa: QA Issue: crank rdepends
> on libasound, but it isn't a build dependency, missing alsa-lib in DEPENDS
> or PACKAGECONFIG? [build-deps]
 
That message is slightly misleading - in this case it really is just a runtime
dependency (since you're not building anything) and you should be able to
resolve it by setting RDEPENDS_${PN} rather than DEPENDS.

> > * As another responder pointed out, the inherit of pkgconfig isn't needed
> > - you don't need pkg-config for anything being done here. 
>
> Again, same error with or without this. Or even if I use " inherit bin_package"

Again, this isn't related to those errors, pkg-config just isn't necessary
for what this recipe does. 

FYI, bin_package is more suited to packages whose layout is already prepared
for the target (e.g. if you had an rpm or deb file) - you could have used it
here, but I'm not entirely sure it would have made things much easier given
the issues you ran into.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre