**** BEGIN LOGGING AT Sat Feb 13 02:59:58 2016
Feb 13 07:07:47 <archer121> Hey, WHen I set a cmake flag in my recipe, is it possible for me to confirm if it worked? Or in other words, I just want to see the cmake output.
Feb 13 08:12:07 <rtr_> Hi. Is there a command to list QA warnings?
Feb 13 08:18:45 <JaMa> cat tmp-eglibc/qa.log
Feb 13 08:19:09 <JaMa> rtr_: but not all QA warnings are listed there
Feb 13 09:36:06 <rtr_> @JaMa Thanks
Feb 13 09:52:48 <aravinPV> Hello, I am trying to compile opencv with cuda support. So what I did is to create my own layer with higher priority, copy opencv recipe from meta-oe and added -DWITH_CUDA=ON to EXTRA_OECMAKE. But the opencv that gets compiled doesnot have cuda support
Feb 13 09:53:14 <aravinPV> I am asked to set the WITH_CUDA=ON cmake flag.
Feb 13 10:10:27 <aravinPV> I tried EXTRA_OECMAKE = "-DWITH_CUDA=ON" and got this error: CMake Error: The source directory "/run/media/fury/storage/yocto/poky/build/tmp/work/cortexa15hf-vfp-neon-poky-linux-gnueabi/cudacv/3.0+gitAUTOINC+424c2bddb3-r0/build/-D WITH_CUDA=ON" does not exist. while do_configure
Feb 13 10:39:15 <aravinPV> issue solved
Feb 13 10:53:45 <rtr_> How do I rebuild all the dependencies along with the main recipe?
Feb 13 10:54:51 <JaMa> why would you want that?
Feb 13 10:55:45 <JaMa> you can delete tmpdir and sstate-cache
Feb 13 10:59:16 <rtr_> @JaMa One of the recipes is failing when compiled individually but passing when other recipe which depends on it is compiled
Feb 13 10:59:34 <rtr_> Just want to recompile everything in that line
Feb 13 11:08:48 <JaMa> maybe it's trying to use some file from WORKDIR of the dependencies, so just fix the recipe
Feb 13 11:14:56 <rtr_> @JaMa will removing sstate-cache remove everything?
Feb 13 11:15:12 <rtr_> All the recipes get rebuilt from scratch?
Feb 13 11:16:29 <aravinPV> hello, anyone have any idea whta DEBUG: Removing manifest: <file> in log.do_compile mean? Will it be a problem?
Feb 13 11:18:33 <JaMa> rtr_: yes
Feb 13 12:26:51 <aravinPV> Hello, this is my first recipe. It is a simple one which installs a binary from a .deb file. Can anyone please take a look and identify the mistakes?
Feb 13 12:26:52 <aravinPV> https://paste.ubuntu.com/15035420/
Feb 13 12:43:28 <aravinPV> why is the package not being created?
Feb 13 13:10:35 <aravinPV> If I am writing a recipe to install binaries from a .deb file, do I have to write the do fetch?
Feb 13 13:36:48 <aravinPV> I am trying to write a simple recipe that installs a few files to /usr from a .deb file. This is the recipe I wrote: https://paste.ubuntu.com/15035766/ and this is the error I get:  https://paste.ubuntu.com/15035771/ Will somebody please point out what is wrong?
Feb 13 14:12:12 <aravinPV> hey, package is there in build/temp/deploy/deb, so why is it not getting installed?
Feb 13 14:20:49 <aravinPV> yay! I found a clue!!!'
Feb 13 14:21:47 <aravinPV> So -dev and -dbg packages are boing installed but not the actual package itself. And I can't install the -dev package because it lists the original package as a dependancy
Feb 13 14:45:41 <aravinPV> I want to package whatever is in my  ${WORKDIR}/output  but doing a FILES_${PN}-dev = "${WORKDIR}/output" didnot work.
Feb 13 14:48:59 <aravinPV> where is everybody?
Feb 13 14:52:02 <fl0v0> how do you install the package? Is it install in a image recipe or in local.conf?
Feb 13 14:52:45 <fl0v0> there is a big difference of the package being build and the package being isntalled
Feb 13 14:53:10 <fl0v0> aravinPV:
Feb 13 14:53:35 <aravinPV> local.conf
Feb 13 14:54:51 <aravinPV> The package being build does not have the files I want to be installed. I have opened them and checked, fl0v0
Feb 13 14:55:50 <fl0v0> you need to add the files in the recipe
Feb 13 14:56:55 <fl0v0> FILES_${PN} += " "
Feb 13 14:57:05 <fl0v0> have you done that?
Feb 13 14:57:16 <aravinPV> This is the part where I am confused.
Feb 13 14:57:40 <aravinPV> I have tried many variations of the above said thing, but none worked
Feb 13 14:58:33 <fl0v0> there are many recipes who do this, maybe just 'grep -r FILES_'  in your source folder
Feb 13 14:58:33 <aravinPV> my ${WORKDIR}/output has "/usr/..." so how should FILES_${PN} look
Feb 13 14:59:09 <fl0v0> you dont use hard coded pathnames
Feb 13 14:59:53 <fl0v0> see here: http://docs.openembedded.ru/directories_installation.html
Feb 13 14:59:56 <aravinPV> Why is FILES_${PN}-dev = "/" should do the job, right?
Feb 13 15:01:52 <aravinPV> fl0v0: Ok, I am tryinh  FILES_${PN}-dev = "${prefix}"
Feb 13 15:01:53 <fl0v0> are we talking of the recipe above?  https://paste.ubuntu.com/15035766/ dont use those pathes
Feb 13 15:02:14 <fl0v0> normaly you do not install anything in your root
Feb 13 15:02:21 <fl0v0> what are you trying to do?
Feb 13 15:02:28 <aravinPV> In desperation I tried those.
Feb 13 15:02:41 <aravinPV> I will post my updated recipe
Feb 13 15:03:33 <aravinPV> https://paste.ubuntu.com/15036462/
Feb 13 15:04:08 <aravinPV> I have some binaries from nvidia in the .deb format.
Feb 13 15:04:15 <aravinPV> I want to install them
Feb 13 15:05:39 <fl0v0> ok idnt really now how one handles precompiled packages
Feb 13 15:05:55 <fl0v0> maybe there is a class for this
Feb 13 15:06:35 <aravinPV> SImply tell me how to do this. Whatever I want to package is present in ${WORKDIR}/output. SO how will my FILE variable look like?
Feb 13 15:08:04 <aravinPV> fl0v0:
Feb 13 15:09:16 <fl0v0> is there a source distribution of the software you want to install? this would it make easer for me
Feb 13 15:10:04 <fl0v0> if not
Feb 13 15:10:28 <fl0v0> the simples way to do it right now would be set the package management of your build to deb
Feb 13 15:10:41 <fl0v0> than copy the file tou your build image and try to install it
Feb 13 15:11:01 <aravinPV> no they are proprietary binaries whose source I don't have
Feb 13 15:11:19 <fl0v0> kk i dont have experience of how to ship blobs
Feb 13 15:12:07 <aravinPV> I am kinda stuck. I have tried what you said. It works like a charm. But this thing is a depandancy for something else that  want to build.
Feb 13 15:13:55 <aravinPV> and the irony is that I am stuck with something so simple!
Feb 13 15:14:27 <fl0v0> look if you can find an installer for deb packages
Feb 13 15:15:02 <aravinPV> what do you mean by installer?
Feb 13 15:15:02 <fl0v0> i dont know if tsometjhing like that exists
Feb 13 15:15:19 <aravinPV> on yocto?
Feb 13 15:15:31 <fl0v0> then you could use 'inherit deb'in your recipe
Feb 13 15:16:03 <aravinPV> bin_package exists
Feb 13 15:16:05 <aravinPV> http://yocto.yoctoproject.narkive.com/yoITgHc1/installing-deb-file-in-build
Feb 13 15:17:20 <fl0v0> yeah that sounds good
Feb 13 15:17:53 <fl0v0> look at classes/bin_package.bbclass thats a good advice
Feb 13 15:18:47 <fl0v0> ok you need to extract the files in the deb
Feb 13 15:18:57 <fenrig> Hi i cant remember the name of the network manager made by intel (for embedded use) for yocto :D
Feb 13 15:19:03 <fenrig> can somebody help refresh my mind
Feb 13 15:19:17 <fl0v0> was it connman ?
Feb 13 15:19:27 <fenrig> yeah I think so
Feb 13 15:19:45 <fenrig> https://01.org/connman
Feb 13 15:19:48 <fenrig> its this one
Feb 13 15:20:03 <aravinPV> is it not done by base.class? I see them in ${WORKDIR}/output
Feb 13 15:20:22 <aravinPV> it is already extracted to ${WORKDIR}/output
Feb 13 15:20:29 <fl0v0> ah ok
Feb 13 15:20:39 <fl0v0> so maybe set S to ${WORKDIR}/output
Feb 13 15:20:48 <fl0v0> S = "${WORKDIR}/output"
Feb 13 15:21:05 <fl0v0> then also inherit from bin_package3
Feb 13 15:21:09 <fl0v0> -3
Feb 13 15:21:54 <fl0v0> then base class should extract your package and bin_package installs it
Feb 13 15:22:03 <fl0v0> but
Feb 13 15:22:04 <fl0v0> moment
Feb 13 15:22:09 <fl0v0> it uses tar
Feb 13 15:22:52 <fl0v0> so you need a tar archive with the binaries
Feb 13 15:23:52 <aravinPV> I added the S parameter and something happened
Feb 13 15:24:06 <fl0v0> ok :)
Feb 13 15:24:16 <aravinPV> do_package_qa failed
Feb 13 15:24:32 <fl0v0> can you pastebin your current recipe?
Feb 13 15:25:33 <aravinPV> wait a sec
Feb 13 15:25:50 <aravinPV> https://paste.ubuntu.com/15036633/
Feb 13 15:27:08 <aravinPV> https://paste.ubuntu.com/15036639/ -> looks like this contains something
Feb 13 15:27:57 <fl0v0> ok
Feb 13 15:29:21 <fl0v0> hmm now you dont need FILES_${PN} = "/*" in the recipe anymore
Feb 13 15:29:32 <fl0v0> but thats not the problem
Feb 13 15:29:49 <fl0v0> i think
Feb 13 15:30:28 <fl0v0> hm the recipes looks good to me
Feb 13 15:31:56 <aravinPV> :-(
Feb 13 15:33:45 <aravinPV> I silenced the "already stripped" QA errror by adding INSANE_SKIP_${PN} = "already-stripped" to my recipe
Feb 13 15:35:30 <fl0v0> does it work?
Feb 13 15:36:05 <aravinPV> !!YES!!
Feb 13 15:36:15 <fl0v0> ncie
Feb 13 15:36:34 <fl0v0> well it builds :)
Feb 13 15:36:34 <aravinPV> thanks a lot!
Feb 13 15:36:45 <aravinPV> so the problem was that S was not set
Feb 13 15:36:53 <fl0v0> ok
Feb 13 15:37:03 <aravinPV> for bin_package to work on
Feb 13 18:27:50 <archer121> CUDA is a build dependency for OpenCV when it is compiled with CUDA support. CUDA binaries are available from nvidia as .deb files. So what I did was to create a recipe that unpacks this deb and install the binaries. Then I added this as a build dependency(DEPENDS) for opencv. Also I set the WITH_CUDA=ON flag for opencv's cmake. But still cmake output (from do_configure logs) indicate that CUDA support has not been turned on. This 
Feb 13 18:28:13 <archer121> has failed to locate the binaries. What possibly when wrong? How to fix it?
Feb 13 18:36:28 <JaMa> anyone else seeing perl build failures? 5.3.0/ld: cannot find -lssp_nonshared
Feb 13 18:39:17 <archer121> Also where is the staging area where I can inspect?
Feb 13 19:02:52 <nerdboy> JaMa: i did, but in another context...
Feb 13 19:03:44 <JaMa> nerdboy: ty, I have a fix already, it was something in my config
Feb 13 19:04:22 <JaMa> we have bbclass preventing staging static libraries unless explicitly whitelisted (to prevent licensing issues)
Feb 13 19:04:26 <nerdboy> are you even building with ssp?
Feb 13 19:04:45 <JaMa> and new perl seems to be first recipe which require libssp_nonshared.a
Feb 13 19:05:45 <nerdboy> perl needs a diaper...
Feb 13 20:59:40 <mikecarp> I am getting this weird issue
Feb 13 20:59:48 <mikecarp> I have this warning:
Feb 13 20:59:50 <mikecarp> cuda-npp-6-5: found library in wrong location: /usr/local/cuda-6.5/targets/armv7-linux-gnueabihf/lib/libnppi.so.6.5
Feb 13 21:00:37 <mikecarp> cuda-npp-6-5 is a build dep for opencv, but it is not there in the sysroot!
Feb 13 21:00:48 <mikecarp> even after there is this warning.
Feb 13 21:01:28 <mikecarp> in short, there is no /usr/local/cuda-6.5/targets/armv7-linux-gnueabihf/lib/libnppi.so.6.5 in the sysroot
Feb 13 21:01:36 <mikecarp> I am puzzled
Feb 13 21:17:11 <mikecarp> But they appear in the correct position in th final image,
**** ENDING LOGGING AT Sun Feb 14 02:59:58 2016