**** BEGIN LOGGING AT Tue Oct 20 02:59:58 2015
Oct 20 06:44:23 <abelal> morning fellas
Oct 20 07:14:49 <bluelightning> morning all
Oct 20 09:41:04 <t0mmy_> Hello everyone
Oct 20 09:56:00 <Ox4> hello yocto-gurus :)
Oct 20 09:57:50 <Ox4> I have the following recipe: http://dpaste.com/3GKSFM3 and after trying to build it I receive the following errors: http://dpaste.com/1R402EJ
Oct 20 09:57:57 <Ox4> could somebody help me?
Oct 20 10:01:01 <bluelightning> Ox4: try adding a line setting INITSCRIPT_NAME to a dummy value
Oct 20 10:02:10 <Ox4> bluelightning: dummy value?
Oct 20 10:02:18 <bluelightning> actually, forget that
Oct 20 10:02:22 <bluelightning> shouldn't  be necessary
Oct 20 10:03:08 <bluelightning> er
Oct 20 10:03:24 <bluelightning> the suffix you're adding to INITSCRIPT_NAME and INITSCRIPT_PARAMS should be a package name
Oct 20 10:03:41 <bluelightning> are ${PN}-powerbeacon and ${PN}-watchdog actually in PACKAGES?
Oct 20 10:03:47 <bluelightning> if not, that is why it is not working
Oct 20 10:03:55 <Ox4> can I use it like this one: INITSCRIPT_NAME-watchdog = "watchdog" ?
Oct 20 10:04:43 <Ox4> watchdog in a SRC_URI="file://" and powerbeacon.sh in a package
Oct 20 10:04:51 <bluelightning> If you use INITSCRIPT_NAME_watchdog but then *only* if "watchdog" is in PACKAGES (and it would not be sensible to do have this recipe produce a package called simply "watchdog")
Oct 20 10:05:36 <Ox4> bluelightning: hm
Oct 20 10:05:39 <bluelightning> the way update-rc.d.bbclass works, you cannot have more than one initscript per package; you can have more than one in the same recipe but they have to be in separate packages
Oct 20 10:06:58 <Ox4> bluelightning: here is the full recipe: http://dpaste.com/12T5P5S
Oct 20 10:07:20 <Ox4> understood, thank you
Oct 20 10:07:33 <bluelightning> the second SRC_URI line is wiping out the first, btw
Oct 20 10:07:59 <bluelightning> either set them both in the same assignment statement or use += in the second one
Oct 20 10:10:11 <Ox4> I'll make a separate packages
Oct 20 10:10:19 <Ox4> bluelightning: thank you for the support
Oct 20 10:13:43 <bluelightning> Ox4: fix your typos as well "defautls"
Oct 20 10:18:19 <Ox4> bluelightning: fixed :)
Oct 20 10:18:23 <Ox4> bluelightning: http://dpaste.com/2JRW78Y
Oct 20 10:18:55 <raykinsella78> vim puts tabs where I want spaces and vica-versa
Oct 20 10:19:25 <bluelightning> Ox4: quite clearly not fixed
Oct 20 10:19:31 <bluelightning> Ox4: latest version of the recipe?
Oct 20 10:20:00 <Ox4> bluelightning: http://dpaste.com/2D2W119
Oct 20 10:20:43 <bluelightning> Ox4: as I wrote above your SRC_URI needs fixing
Oct 20 10:21:15 <Ox4> ah
Oct 20 10:21:16 <Ox4> +=
Oct 20 10:21:17 <Ox4> ok
Oct 20 10:21:20 <bluelightning> Ox4: also as I said you don't need a separate recipe, just a separate package in the same recipe
Oct 20 10:23:27 <Ox4> bluelightning: but actually I build my watchdog separatly and I think I is better to install the script to init.d directory in this recipe as well
Oct 20 10:23:51 <Ox4> bluelightning: hm, the same error :-(
Oct 20 10:24:20 <Ox4> bluelightning: I just changed SRC_URI += "file://watchdog"
Oct 20 10:24:46 <bluelightning> do you have a "watchdog" file in a subdir next to the recipe?
Oct 20 10:25:00 <Ox4> bluelightning: sure
Oct 20 10:25:03 <Ox4> http://dpaste.com/2ZHKVJW
Oct 20 10:25:14 <bluelightning> oh
Oct 20 10:25:30 <bluelightning> wait... you're checking out a directory called watchdog, and the file is also called watchdog
Oct 20 10:25:33 <bluelightning> that's not going to work
Oct 20 10:25:48 <bluelightning> rename the file to watchdog.init perhaps
Oct 20 10:25:50 <Ox4> bluelightning: here is the directory tree: http://dpaste.com/35WJAB1
Oct 20 10:26:08 <Ox4> hm
Oct 20 10:26:09 <Ox4> ok
Oct 20 10:26:21 <bluelightning> doesn't actually matter what the file is called at source since you can specify what it should be called at the destination in the install line
Oct 20 10:26:57 <bananadev> watchdog is file name and folder name also?
Oct 20 10:28:10 <Ox4> http://dpaste.com/0V2DX11
Oct 20 10:28:47 <Ox4> ok, I will do one recipe for all scripts
Oct 20 10:29:06 <bluelightning> Ox4: your install line source path is wrong
Oct 20 10:29:40 <bluelightning> Ox4: you know, if you read the error messages and look in the workdir for the recipe to see where files are going, you'll have a much easier time...
Oct 20 10:31:06 <Ox4> bluelightning: yes, I know, but how can I copy the sript from files directory?
Oct 20 10:31:28 <CTtpollard> Hi, if I'm doing multiple builds for different boards on the same build machine is there anything I can do to share components between builds beyond sharing a dl_dir in local conf?
Oct 20 10:31:30 <bluelightning> Ox4: it is being copied
Oct 20 10:32:21 <bluelightning> Ox4: but you're telling it to install the script from ${S}, that's not where it is - it's in ${WORKDIR}
Oct 20 10:34:48 <rburton> CTtpollard: share DL_DIR and SSTATE_DIR
Oct 20 10:34:49 <Ox4> bluelightning: I've tried to use .., but it doesn't work
Oct 20 10:34:52 <Ox4> install -m 0755 /home/vadimi/yocto/poky/build/tmp/work/cortexa8-vfp-neon-poky-linux-gnueabi/powerbeacon-watchdog/1.0-r0/watchdog/../watchdog.init /home/vadimi/yocto/poky/build/tmp/work/cortexa8-vfp-neon-poky-linux-gnueabi/powerbeacon-watchdog/1.0-r0/image/etc/init.d/watchdog
Oct 20 10:35:03 <Ox4> bluelightning: anyway, thank you for the hint
Oct 20 10:35:14 <bluelightning> Ox4: why use ..? just use ${WORKDIR}
Oct 20 10:35:18 <CTtpollard> rburton: I'll take a deeper look into sstate_dir, thanks
Oct 20 10:39:08 <Ox4> bluelightning: install: cannot create regular file '/home/vadimi/yocto/poky/build/tmp/work/cortexa8-vfp-neon-poky-linux-gnueabi/powerbeacon-watchdog/1.0-r0/image/etc/init.d/watchdog': No such file or directory
Oct 20 10:39:35 <Ox4> bluelightning: http://dpaste.com/38HE02Y
Oct 20 10:40:19 <Ox4> ah
Oct 20 10:40:24 <Ox4> INITSCRIPT_NAME
Oct 20 10:40:41 <bananadev> Do you create directory etc/init.d
Oct 20 10:41:13 <bananadev> before install watchdog.init
Oct 20 10:41:27 <Ox4> install -d ${D}{sysconfdir}/init.d
Oct 20 10:41:29 <Ox4> yes
Oct 20 10:41:34 <Ox4> it is in do_install function
Oct 20 10:41:59 <bananadev> you miss '$' at sysconfdir
Oct 20 10:42:10 <Ox4> omg
Oct 20 10:42:11 <Ox4> thanks
Oct 20 10:51:40 <Ox4> I have another question
Oct 20 10:52:27 <Ox4> I set INITSCRIPT_PARAMS = "defaults" for another script but I don't see any symlink to it in /etc/rc#.d
Oct 20 10:59:44 <bananadev> It will be executed when you install your package to rootfs
Oct 20 11:31:23 <Ox4> anyway I don't see the symlinks in runlevels directories for this script
Oct 20 11:47:54 <Ox4> Also is there a documentation how to build custom u-boot?
Oct 20 11:52:26 <CTtpollard> what's the difference between SSTATE_DIR & SSTATE_MIRRORS if you point them to the same local dir?
Oct 20 11:56:39 <bluelightning> CTtpollard: you wouldn't point them to the same local dir, that wouldn't accomplish anything (and may break things)
Oct 20 11:57:34 <CTtpollard> from the comments in localconf I can't really parse the difference between the two options
Oct 20 11:59:43 <CTtpollard> is there anywhere I can look for the explanation?
Oct 20 12:05:06 <bluelightning> CTtpollard: you could look at http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-SSTATE_MIRRORS
Oct 20 12:06:05 <bluelightning> CTtpollard: ultimately though SSTATE_DIR is the local directory where sstate artifacts will be written to and read from, SSTATE_MIRRORS points to one or more locations to try to read sstate artifacts from
Oct 20 12:06:19 <bluelightning> the latter may be remote
Oct 20 12:20:34 <CTtpollard> bluelightning: so, if I want to share a local state artifacts between builds on the same machine, I should just use sstate_dir?
Oct 20 12:20:49 <bluelightning> CTtpollard: you can do that yes
Oct 20 12:21:21 <CTtpollard> but then all builds would write to it, where as I could have only one write to it and the others just pull from it with sstate_mirrors?
Oct 20 12:22:05 <bluelightning> you could set it up either way; we've taken steps to ensure that you won't get partially-written files, so concurrent access should be fine
Oct 20 12:23:07 <CTtpollard> bluelightning: thanks for the, I understand the R/W difference between the two now
Oct 20 12:23:13 <CTtpollard> *the help
Oct 20 12:24:04 <qknight> hey. i want to have qmake and development tools from qt in my target system using yocto. how to do that?
Oct 20 12:25:29 <bluelightning> CTtpollard: no problem
Oct 20 12:29:11 <bluelightning> qknight: qt4-tools is the package contains qmake + other tools
Oct 20 12:29:18 <qknight> i want tqt5
Oct 20 12:29:24 <qknight> i meant qt5, sorry
Oct 20 12:29:36 <LetoThe2nd> qknight: have a good look at meta-qt5, then
Oct 20 12:30:06 <qknight> LetoThe2nd: i'm on daisy and there is not meta-qt5 as far as i can tell
Oct 20 12:30:24 <qknight> LetoThe2nd: nativesdk-packagegroup-qt5-toolchain-host <- maybe this?
Oct 20 12:30:52 <LetoThe2nd> qknight: https://github.com/meta-qt5/meta-qt5 tells something different
Oct 20 12:32:11 <qknight> LetoThe2nd: oh, of course you are refering to the meta-qt5 repository
Oct 20 12:32:20 <LetoThe2nd> what else?
Oct 20 12:32:28 <qknight> LetoThe2nd: i have that already included and qtbase installed but that qtbase won't pull qmake for instance
Oct 20 12:33:02 <qknight> LetoThe2nd: what else? in gentoo some packages were called foo-meta so that they pull in all kinds of other packages, hence the name. for instance this was used with kde-meta to install all of kde4 applications
Oct 20 12:33:20 <bluelightning> qknight: qtbase-tools ?
Oct 20 12:33:20 <LetoThe2nd> qknight: well i said meta-qt5, i thought its obvious i meant the layer.
Oct 20 12:33:38 <bluelightning> LetoThe2nd: if you're new-ish to the project, probably not
Oct 20 12:33:52 <LetoThe2nd> and https://github.com/meta-qt5/meta-qt5/tree/daisy/recipes-qt/qt5 suggests that there's qttools for daisy, version 5.2.1
Oct 20 12:33:53 <qknight> LetoThe2nd: nativesdk-qttools maybe? i post the complete list, wait a second
Oct 20 12:33:55 <LetoThe2nd> bluelightning: yeah, maybe
Oct 20 12:34:23 <bluelightning> to complicate things we also use meta- in the other way as well (not very often, but in places)
Oct 20 12:34:47 <LetoThe2nd> qknight: nativesdk is something else.
Oct 20 12:34:55 <bluelightning> qknight: nativesdk-* are for the host part of the SDK, not for the target
Oct 20 12:34:56 <LetoThe2nd> qknight: have you checked the qttools package?
Oct 20 12:34:59 <qknight> LetoThe2nd: anyway, thanks very much. i think i will try a few of the packages ;-)
Oct 20 12:35:29 <qknight> LetoThe2nd: qttools or qttools-native?
Oct 20 12:35:38 <bluelightning> -native is for the build host
Oct 20 12:35:43 <qknight> LetoThe2nd: never installed qttools yet
Oct 20 12:35:45 <qknight> LetoThe2nd: ok, thanks!
Oct 20 12:36:27 <LetoThe2nd> qknight: thats at least my bet.
Oct 20 12:55:15 <Ox4> guys how can I add custom u-boot for my machine?
Oct 20 12:55:34 <qknight> Ox4: freescale board?
Oct 20 12:55:41 <Ox4> qknight: nope :-(
Oct 20 12:55:49 <Ox4> our own board
Oct 20 12:56:01 <qknight> Ox4: ok, then ask yourself? ;-)
Oct 20 12:56:09 <qknight> Ox4: srly, you have probably two options
Oct 20 12:56:19 <Ox4> qknight: ?
Oct 20 12:56:29 <qknight> Ox4: either using a sd-card where the u-boot is on or using an internal flash where the u-boot is in
Oct 20 12:56:35 <qknight> Ox4: which board is that exactly?
Oct 20 12:56:45 <Ox4> I am going to append my own recipe but I doubt that it is the correct way
Oct 20 12:57:09 <qknight> Ox4: depends on the board and how the image is built
Oct 20 12:57:12 <Ox4> qknight: it has internal flash
Oct 20 12:57:27 <qknight> Ox4: on arm you can use the target 'sdcard' and then it 'can' include the u-boot
Oct 20 12:58:20 <qknight> Ox4: often you can switch between internal flash uboot and sd-card uboot using a switch on the board, is there one?
Oct 20 13:01:07 <Ox4> qknight: yes I have an ARM architecture, but I have own source of u-boot and its config
Oct 20 13:01:30 <Ox4> qknight: should I write my own recipe for it?
Oct 20 13:01:44 <qknight> Ox4: first find out who the uboot is loaded
Oct 20 13:02:47 <Ox4> qknight: what do you mean?
Oct 20 13:04:26 <LetoThe2nd> you have a littel discrepancy here. Ox4 is talking about building the u-boot binary, qknight is talking about using it.
Oct 20 13:04:55 <qknight> LetoThe2nd: oh, thanks for pointing out
Oct 20 13:05:00 <LetoThe2nd> Ox4: usually one writes a specific u-boot recipe that fits only the targetted machine
Oct 20 13:05:24 <LetoThe2nd> Ox4: examples: https://github.com/linux4sam/meta-atmel/tree/master/recipes-bsp/u-boot
Oct 20 13:06:04 <LetoThe2nd> Ox4: specifically https://github.com/linux4sam/meta-atmel/blob/master/recipes-bsp/u-boot/u-boot-at91_2014.07.bb
Oct 20 13:06:59 <Ox4> LetoThe2nd: thanks
Oct 20 13:11:11 <qknight> i've added meta-amd and included the common direcotry in my bblayers.conf (my target is a PPC machine with a firegl pcie card). the problem: http://paste.ubuntu.com/12876579/ <- am i supposed to install linux-amd now?
Oct 20 13:12:38 <bluelightning> qknight: is meta-amd actually meant to support those graphics cards or is it meant for AMD SOCs  ?
Oct 20 13:12:53 <bluelightning> I thought the latter, but I'm not sure
Oct 20 13:12:56 <qknight> bluelightning: not really sure. probably only SoC
Oct 20 13:14:50 <LetoThe2nd> looks very much like soc only. probably you'd rather want a proper setup of kernel drivers and mesa etc.
Oct 20 13:15:14 <qknight> LetoThe2nd: thanks for pointing that out!
Oct 20 13:15:22 <qknight> might be a huge time-saver
Oct 20 13:17:21 <LetoThe2nd> can't tell if things are in place and properly supported for ppc in the kernel and mesa, though.
Oct 20 13:19:47 <qknight> LetoThe2nd: i'd like to try. do you have any pointers?
Oct 20 13:21:14 <LetoThe2nd> qknight: like, running menuconfig on kernel source with ARCH set properly, then check what the video/gpu driver options are.
Oct 20 13:21:31 <qknight> LetoThe2nd: exactly! thanks
Oct 20 13:30:34 <qknight> is there a way to speedup the 'parsing recipes:  20% ######" ...?
Oct 20 13:31:26 <LetoThe2nd> qknight: faster disk, more ram?
Oct 20 13:31:36 <LetoThe2nd> stash everything in a tmpfs?
Oct 20 13:31:45 <qknight> LetoThe2nd: yeah, probably the disk inside the VM
Oct 20 13:31:54 <qknight> LetoThe2nd: then the answer for me is: NO ;P
Oct 20 13:31:56 <LetoThe2nd> OMG building inside a vm
Oct 20 13:32:05 <LetoThe2nd> the setup of doom.
Oct 20 13:32:13 <qknight> lol, not at all ;-)
Oct 20 13:32:14 <LetoThe2nd> *SCNR*
Oct 20 13:32:47 <LetoThe2nd> ok, a vm with 64+X GB ram will do the trick nicely, i'd guess. tmpfs then again.
Oct 20 13:33:05 <qknight> already gave it 6gb, can't afford for more ;P
Oct 20 13:33:49 <LetoThe2nd> then no improvement for you, sorry.
Oct 20 13:36:33 <bluelightning> qknight: are you seeing it generally being slow, or is it stalling at certain points for a long time?
Oct 20 13:40:17 <didrocks> hey guys :)
Oct 20 13:40:32 <xnox> bluelightning: introducing didrocks (didier roche).
Oct 20 13:40:45 <bluelightning> hi didrocks
Oct 20 13:40:45 <xnox> didrocks: intorucing #yocto =)
Oct 20 13:40:57 <didrocks> hey bluelightning, thanks xnox!
Oct 20 13:46:21 <qknight> bluelightning: for every: bitbake fsl-image-x11 it takes about 3minutes to parse the recipes
Oct 20 13:46:30 <qknight> bluelightning: is that normal?
Oct 20 13:47:01 <bluelightning> 3 minutes is a little bit longer than I'd expect, and is it absolutely every time or only every time you change the configuration?
Oct 20 13:47:24 <qknight> bluelightning: yes only with changed configuration
Oct 20 13:47:35 <bluelightning> ok, that is how it should be working
Oct 20 13:47:43 <bluelightning> the parsing time will vary with the number of layers you have in bblayers.conf and the number of recipes they contain
Oct 20 14:22:45 <Ox4> http://dpaste.com/2J1J5JK
Oct 20 14:22:56 <Ox4> it is not built :-(
Oct 20 14:25:00 <bluelightning> Ox4: I hope btw you aren't using the same name for your MACHINE as you are that recipe we were discussing earlier
Oct 20 14:26:17 <bluelightning> also, there is a *lot* more to building u-boot than what you're putting in there
Oct 20 14:26:39 <bluelightning> see our own u-boot recipes, which I'd suggest you bbappend (or at least share inc files with)
Oct 20 14:27:07 <Ox4> bluelightning: my MACHINE is powerbeacon
Oct 20 14:27:23 <bluelightning> is that recipe also called  powerbeacon ?
Oct 20 14:29:35 <Ox4> bluelightning: I named it meta-powerbeacon/recipes-bsp/u-boot/u-boot_pb_2014.10.bb
Oct 20 14:29:49 <bluelightning> Ox4: no, the other one we were discussing earlier
Oct 20 14:32:11 <Ox4> bluelightning: do you mean watchdog recipe?
Oct 20 14:33:29 <Ox4> bluelightning: how can I set my own u-boot config file if I will use bbappend?
Oct 20 14:33:44 <bluelightning> I believe so yes, though I'm not an expert
Oct 20 14:34:04 <bluelightning> on building/configuring u-boot
Oct 20 14:34:40 <Ox4> me too :-(
Oct 20 14:34:48 <Ox4> I see it for the first time :D
Oct 20 14:38:44 <bluelightning> Ox4: I would encourage you to have a look at meta/recipes-bsp/u-boot/u-boot.inc and then see if you can bbappend the recipe (or take a copy of the .bb file next to it) and change only the things you need to change
Oct 20 14:47:38 <Ox4> bluelightning: if I want to include it in my recipe do I have to copy it to the directory with my recipe?
Oct 20 14:47:52 <bluelightning> Ox4: no
Oct 20 14:48:32 <bluelightning> Ox4: you need only have  require recipes-bsp/u-boot/u-boot.inc  in the .bb file
Oct 20 14:49:42 <Ox4> thanks
Oct 20 15:05:24 <_4urele_> hello everyone
Oct 20 15:05:49 <_4urele_> did anyone tried to use webkit-gtk with wayland?
Oct 20 15:07:12 <bluelightning> rburton: ^
Oct 20 15:07:49 <rburton> _4urele_: as i understand it, webkit-gtk requires x11 right now
Oct 20 15:08:16 <rburton> _4urele_: http://www.igalia.com/webkitforwayland/ might be useful
Oct 20 15:11:21 <_4urele_> rburton, Thanks a lot! I will take a look at this
Oct 20 15:20:03 <jmesmon> Is there anything that might prevent variables exported in bitbake.conf from being set in .bbappends? (I'm trying to use ${nonarch_libdir}, but it appears to be empty)
Oct 20 15:20:52 <bluelightning> jmesmon: no, that should not be possible
Oct 20 15:21:04 <bluelightning> jmesmon: are you sure your bbappend is actually being applied?
Oct 20 15:21:25 <bluelightning> jmesmon: bitbake -e recipename | less may help you double-check variable values
Oct 20 15:22:47 <jmesmon> bluelightning: I'll check that (might give me a clue), but I'm sure it's being applied: bitbake is complaining about '/modules-load.d/foo.conf' (should be /usr/lib/modules-load.d/foo.conf) which is installed by the append.
Oct 20 15:23:13 <bluelightning> ah ok, fair enough
Oct 20 15:47:29 <neverpanic> What's the easiest way to find out which recipe build a package, when all I have is the package name?
Oct 20 15:48:15 <CTtpollard> grep for the package name in your build env? neverpanic
Oct 20 15:50:34 <neverpanic> CTtpollard: by "build env" you mean my build directory? I was hoping for a solution that produces little to no false positives :/
Oct 20 15:50:51 <neverpanic> and bitbake -e $myimage doesn't even contain the package name I'm looking for.
Oct 20 15:54:28 <CTtpollard> hmm
Oct 20 15:56:33 <CTtpollard> i'm not sure of a cleaner method, but it would be nice to know
Oct 20 16:00:56 <bananadev> neverpanic: you may try bitbake -g packagename, then grep the package in file pn-depends
Oct 20 16:02:57 <kergoth> -g takes a recipe name, not package name
Oct 20 16:03:20 <kergoth> and pn-depends lists PN, which is recipe names, not package names
Oct 20 16:03:36 <kergoth> -e image won't how anything about what packages exist, only what packages your image is installing, which are two different things
Oct 20 16:04:13 <kergoth> either grep for the package name in your layers/recipes, or try my bb tool's search or search-packages subcommands, i'd say
Oct 20 16:04:20 <kergoth> https://github.com/kergoth/bb
Oct 20 16:04:35 <JaMa> halstead: Hi, is there some known issue with openembedded-commits@lists.openembedded.org ? I haven't received any e-mail with new commits for last few weeks
Oct 20 16:04:39 <kergoth> of course, if you've already built the package you want, you could do a find in tmp/deploy/
Oct 20 16:04:58 <bananadev> ah. sorrry. I misunderstood
Oct 20 16:10:10 <neverpanic> kergoth: hm, so find in tmp/deploy, then dpkg -f $file OE would work
Oct 20 16:10:26 <neverpanic> (with ipks and debs, that is)
Oct 20 16:10:42 <kergoth> you're searching for a file? you'd said you had a packaeg name, not file name
Oct 20 16:10:53 <kergoth> if you have af ile name, and you've built what you need, you can use oe-pkgdata-util, which works much better for that
Oct 20 16:11:15 <belen> neverpanic: the easiest way might be toaster, but you will to set it up and then re
Oct 20 16:11:25 <belen> then rebuild the image
Oct 20 16:11:30 <belen> which is a bit of work :)
Oct 20 16:11:53 <kergoth> good point
Oct 20 16:12:30 <neverpanic> I have the dependency information of a package, and I want to map that back into what DEPENDS should have been (because there should not be any cases where something is in RDEPENDS that isn't in DEPENDS)
Oct 20 16:13:57 <neverpanic> oe-pkgdata-util lookup-recipe is exactly what I need, thanks for the hint.
Oct 20 16:14:03 <kergoth> np
Oct 20 16:21:34 <halstead> JaMa, I can look into that in about an hour. Can you forward the last e-mail you received to michael@yoctoproject.org?
Oct 20 16:31:46 <JaMa> halstead: I've bounced last I have in my e-mail folder, but I'm not completely sure it was the very last one (maybe I've deleted some already)
Oct 20 16:32:29 <JaMa> halstead: and I don't know if it's issue with mailmain or git hook
Oct 20 19:33:57 <jozzan> hi, anybody there that would answer me a quick question?
Oct 20 19:36:15 <jozzan> I'm wanting to introduce a package group in one of my recipes and it complains about not having specified the License Field.Is this a necessity for packagegroups?
Oct 20 19:43:06 <neverpanic> It's a necessity for every recipe.
Oct 20 19:43:37 <neverpanic> You can set LICENSE = "CLOSED" to avoid it, or just go for LICENSE = "MIT" because the code in your packagegroup isn't really worth protecting anyway
Oct 20 19:44:34 <fray> there is some argument that there is very little "creative" about a packagegroup recipe (and other recipe contents) so if it even went to court (at least in the US) those parts might be deamed public domain anyway..
Oct 20 19:45:05 <fray> (in the US facts aren't under copyright.. procedures are facts when something can only be done "one way")
Oct 20 19:45:29 <jozzan> okay thanks
Oct 20 20:37:54 <Christian___> Hello, anybody there?
Oct 20 20:39:30 <Christian___> I am currently trying to compile something with the eclipse plugin, it always complains Buildfile generation error occurred.. Build of project failed with the following error: CMake Error: Could not find CMAKE_ROOT !!! CMake has most likely not been installed correctly. Modules directory not found in /mydir/build/tmp/sysroots/x86_64-linux/usr/bin
Oct 20 20:39:46 <Christian___> Any ideas what I could do?
Oct 20 20:46:57 <Christian___> Can anybody help me with the plugin? Currently I am just trying to get the hello world example working. I also installed adt from the web and set it up for the prebuild compiler but there it does not find the crti.o and other files.
Oct 20 20:49:59 <Christian___> I set the path for /opt/poky/1.8 and the other one for the installed root in my home directory
Oct 20 20:54:59 <qknight> LetoThe2nd: bitbake -c menuconfig linux-qoriq
Oct 20 20:55:08 <qknight> LetoThe2nd: should set the correct ARCH automatically?
Oct 20 20:57:54 <Christian___> I would say you need to define it with selecting the  "machine"  in your conf, but I am not an expert ...
Oct 20 20:58:40 <Christian___> like Machine="yourBoardSupportPackage"
Oct 20 20:59:33 <Christian___> little correction: MACHINE = "..."
Oct 20 21:04:29 <neverpanic> Christian___: make sure that there's no file or directory called "cmake" in the directory where you run cmake.
Oct 20 21:05:00 <neverpanic> /mydir/build/tmp/sysroots/x86_64-linux/usr/bin certainly sounds like there could be a cmake binary there.
Oct 20 21:07:35 <Christian___> Ehm, can you first tell me, which should be the correct directories I should select for eclipse plugin when I am using the system derived method?
Oct 20 21:07:42 <Christian___> Maybe I am wrong with that...
Oct 20 21:08:45 <Christian___> currently I have the build for the first and the build/tmp/sysroots/mysysroot is that correct?
Oct 20 21:10:28 <Christian___> by the way there is no such directory it is the standard example from eclipse when you select new c++ project and chose the yocto toolchain
Oct 20 21:16:57 <Christian___> By the way I just got it compiling with the precompiled adt. But I would to need my own sysroot, (because of some installed libraries etc...) , so the example is working but not with my derived toolchain. I also can not use the precompiled with my extracted sysroot from my system: /opt/poky/1.8/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld: cannot find crtbegin.o: No such fil
Oct 20 21:20:33 <Christian___> neverpanic /mydir/build/tmp/sysroots/x86_64-linux/usr/bin certainly sounds like there could be a cmake binary there. -> Yes there is one in there
Oct 20 21:20:53 <neverpanic> yeah, try running your cmake command elsewhere.
Oct 20 21:21:19 <neverpanic> I have absolutely no idea about anything related to the eclipse plugin
Oct 20 21:21:35 <neverpanic> But I did previously debug that cmake behaves weird as soon as it finds a cmake binary in the current directory
Oct 20 21:21:59 <neverpanic> Basically it assumes that this must be the binary that you ran (even if it isn't) and continues to try to locate its auxillary files relative to that path
Oct 20 21:22:15 <neverpanic> and when it fails to do that, you see the "Could not find CMAKE_ROOT" warning
Oct 20 21:25:24 <Christian___> Hmm ok I will try to move it out there just for a test
Oct 20 21:28:33 <neverpanic> the correct solution would probably be to adjust some other path rather than change your sysroot
Oct 20 21:29:09 <Christian___> neverpanic you were right ... with cmake in there its this error. Without it, it is the other one. /opt/poky/1.8/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld: cannot find crtbegin.o: No such file or directory /opt/poky/1.8/sysroots/x86_64-pokysdk-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/ld: cannot find -lgcc
Oct 20 21:35:20 <neverpanic> that latter thing seems to be a library search path issue. Make sure you're actually using the right compiler
Oct 20 21:40:20 <Christian___> Ok I had it working now, till, I copied the cmake back to the place ... WTF? Am I supposed to use myImage-tcbootstrap? O_o
Oct 20 21:41:50 <neverpanic> No, you're supposed to run cmake in a different directory. I have no idea how you change the working directory of whatever you are doing, but it cannot have a cmake file in it
Oct 20 21:43:39 <Christian___> I have not changed it myself. Somehow eclipse or the cmake files in there have ... I have not created any of these files myself.
Oct 20 21:45:49 <Christian___> Btw do you know what are these sysroots  for? x86_64-linux x86_64-nativesdk-pokysdk-linux x86_64-nativesdk-pokysdk-linux-tcbootstrap
Oct 20 21:47:38 <neverpanic> well, x86_64-linux is probably your target system, x86_64-nativesdk-pokysdk-linux is for stuff you build for your SDK (which seems to be x86_64 as well) and the -tcbootstrap one is (I think, not sure about that) for bootstrapping some libc stuff
Oct 20 21:49:47 <Christian___> actually x86_64 is not my target, but there is no sdk for my machine then O_o there is no dir myMachine-sdk
Oct 20 21:50:47 <fray> x86_64-linux is your host.. (native)  x86_64-nativesdk-pokysdk-linux is the targeted SDK you re building.. the 'tcbootstrap' is for some intermediate files that are needed to build an SDK toolchain
Oct 20 21:51:22 <fray> (native packages are specific to the build system and environment and generally are not deployed or shared)
Oct 20 21:54:01 <Christian___> Hmm ok ...
Oct 20 21:54:34 <Christian___> Now the question is, why does it create a cmake binary in that directory, when I move it, it seems to work.
Oct 20 21:55:06 <Christian___> build/tmp/sysroots/x86_64-linux/usr/bin
Oct 20 21:57:02 <Christian___> neverpanic By the way thanks so far, that helps me a lot, spend two weeks now, with trying things to get it compile again ;-)
Oct 21 02:23:54 <qknight> yay, built my own kernel and deployed it and then discovered that i don't have the firmware installed radeon/R600_rlc.bin
**** ENDING LOGGING AT Wed Oct 21 02:59:58 2015