**** BEGIN LOGGING AT Fri Nov 10 03:00:00 2017
Nov 10 04:18:49 <bodangly> EXTRA_USERS_PARAMS - does this support the full range of usermod options?
Nov 10 04:19:51 <bodangly> ie -L for disabling password login, -s for setting a shell (ie /usr/sbin/nologin'
Nov 10 07:34:10 <yocti> New news from stackoverflow: How to conditionally specify a variable in yocto .bb recipe <https://stackoverflow.com/questions/42093482/how-to-conditionally-specify-a-variable-in-yocto-bb-recipe>
Nov 10 07:58:31 <ranran> Does anyone know how to add servers to smart list ?
Nov 10 09:05:17 <ranran> Is there a difference between build and compile ?
Nov 10 09:05:20 <ranran> in yocto terms
Nov 10 09:19:01 <ranran> build a package and install a package is the same ?
Nov 10 09:20:13 <LetoThe2nd> no
Nov 10 09:20:46 <LetoThe2nd> compile and build share some semantic meaning. i would say building includes compiling
Nov 10 09:20:57 <LetoThe2nd> installing something is different
Nov 10 09:21:03 <ranran> Let2The2nd, thanks that make sense
Nov 10 09:21:43 <ranran> I somewhere read the following "you can't build a rootfs without packages.  You can't build a package until you install. You can't install until you compile. You can't compile until you configure.  You can't configure until you've patched.  You can't patch until you unpack.  You can't unpack until you fetch."
Nov 10 09:22:01 <ranran> I don't understand " You can't build a package until you install" . Is that an error ?
Nov 10 09:22:41 <ranran> build and compile is the same, so building the package is before installing it.
Nov 10 09:23:30 <ranran> I think it should be "You can't build rootfs until you install all packages". Right ?
Nov 10 09:24:46 <LetoThe2nd> thats because the word "build" is used in at least 3 different meanings in the last two posts.
Nov 10 09:25:19 <LetoThe2nd> 1. building a rootfs is the process of constructing the filesystem layout, which uitlizes the prepared packages.
Nov 10 09:25:56 <LetoThe2nd> 2. building a package is creating a well-defined archive out of artifacts that come from some preliminary step
Nov 10 09:26:40 <LetoThe2nd> 3. building a recipe usually refers to compiling the source, but depending on the actual thing it might also have different implications
Nov 10 09:26:53 <LetoThe2nd> hence, jsut don't use "build", but say exactly what you want
Nov 10 09:37:15 <ranran> LetoThe2nd, usually install a package is the process which create the archive ?
Nov 10 09:38:42 <LetoThe2nd> ranran: the do_install step is the first part of the package archive creation
Nov 10 09:39:42 <LetoThe2nd> ranran: do a bitbake -c listtasks for the recipe that you are interested in, then you see whats going on with some short descriptions
Nov 10 11:18:12 <T_UNIX> hi
Nov 10 11:27:28 <rburton> kanavin: have a look at ross/patchmaggeddon
Nov 10 11:55:11 <T_UNIX> am I right in understanding that bitbake does *not* support to specify required package versions besides the volatile conf/local.conf?
Nov 10 11:55:34 <T_UNIX> or rather inappropriate (wrt to image releases) machine.conf?
Nov 10 11:57:10 <T_UNIX> even PREFERRED_VERSION_pn appears to be a recommendation only -.-
Nov 10 12:04:54 <yocti> New news from stackoverflow: systemd recipe for an exsiting executable <https://stackoverflow.com/questions/47222033/systemd-recipe-for-an-exsiting-executable>
Nov 10 12:09:23 <rburton> T_UNIX: RDEPENDS have version constraints, DEPENDS cannot (yet)
Nov 10 12:10:07 <T_UNIX> rburton: so that would be RDEPENDS_myimage += "somepackage-someversion" ?
Nov 10 12:26:44 <xtron> I'm adding a yocto-layer and want to include my helloworld.c fill in the core-image, getting error of unable to locate the package, can anyone help?
Nov 10 12:30:15 <LetoThe2nd> xtron: 1) did you add the layer? 2) how is the package called that should compile the .c file?
Nov 10 12:30:42 <LetoThe2nd> xtron: IIRC there is the yocto-layer create command that asks if it should provide an example, which would be exactly that
Nov 10 12:32:38 <xtron> LetoThe2nd: yup I added the layer using <yocto-layer create hello> command, but I change the hello_0.1.bb file
Nov 10 12:33:09 <LetoThe2nd> xtron: did you add the layer then to the conf/bblayers.conf of your build directory?
Nov 10 12:33:42 <xtron> in hello*.bb file I remove all the default components, now I've 4 DESCRIPTION = "This is custom yocto image"
Nov 10 12:33:45 <xtron>   5 LICENSE = "MIT"
Nov 10 12:33:48 <xtron>   6 SECTION = "images"
Nov 10 12:33:50 <xtron>   7
Nov 10 12:33:53 <xtron>   8 # Core files for basic console boot
Nov 10 12:33:55 <LetoThe2nd> xtron: no need to paste it here.
Nov 10 12:33:55 <xtron>   9 IMAGE_INSTALL = "packagegroup-core-boot"
Nov 10 12:33:58 <xtron>  10
Nov 10 12:34:00 <xtron>  11 # Add desired packages
Nov 10 12:34:03 <xtron>  12 IMAGE_INSTALL += "psplash dropbear hello"
Nov 10 12:34:05 <xtron>  13
Nov 10 12:34:08 <xtron>  14 inherit core-image
Nov 10 12:34:10 <xtron>  15
Nov 10 12:34:11 <LetoThe2nd> xtron: *sigh* for things like that, use a pastebin.
Nov 10 12:34:13 <xtron>  16 IMAGE_ROOTFS_SIZE ?= "8192"
Nov 10 12:34:49 <LetoThe2nd> and try to answer my question, please.
Nov 10 12:34:59 <yocti> New news from stackoverflow: systemd yocto recipe for an existing executable <https://stackoverflow.com/questions/47222033/systemd-yocto-recipe-for-an-existing-executable>
Nov 10 12:35:16 <xtron> LetoThe2nd: yes I added layer in conf/bblayers.conf
Nov 10 12:35:41 <LetoThe2nd> xtron: then what does bitbake hello give you?
Nov 10 12:37:10 <xtron> https://pastebin.com/QtMiiwCf
Nov 10 12:37:17 <xtron> LetoThe2nd: this
Nov 10 12:40:07 <LetoThe2nd> xtron: please also pastebin the complete recipe file after your modification
Nov 10 12:41:07 <xtron> https://pastebin.com/6N1Z5fWT
Nov 10 12:41:36 <LetoThe2nd> xtron: this is certainly not the recipe hello_0.1.bb
Nov 10 12:41:41 <LetoThe2nd> xtron: this is some image
Nov 10 12:42:06 <xtron> LetoThe2nd: what it means?
Nov 10 12:42:06 <LetoThe2nd> xtron: or did you remove the contents of hello_0.1.bb and drop in that image stuff?
Nov 10 12:42:22 <LetoThe2nd> xtron: that is a recipe that creates an image.
Nov 10 12:42:34 <LetoThe2nd> xtron: its image install references a package called "hello"
Nov 10 12:42:46 <LetoThe2nd> xtron: you somewhere, you gotta have a recipe that creates that package
Nov 10 12:42:51 <xtron> LetoThe2nd: I want to make image for x86-64
Nov 10 12:43:16 <xtron> LetoThe2nd: what is wrong, where I'm not getting the point
Nov 10 12:43:52 <xtron> LetoThe2nd: all i want is the final image should have package "hello" which will print the string
Nov 10 12:44:16 <LetoThe2nd> xtron: please remove that layer from your build and create a new one. with the yocto-layer too, and say y to the example, n to the bbappend
Nov 10 12:44:40 <xtron> LetoThe2nd: main do_compile() is defined in bbappend
Nov 10 12:45:06 <LetoThe2nd> xtron: no, thats totally wrong…
Nov 10 12:45:25 <LetoThe2nd> xtron: you have to separate recipes that create images from recipes that create packages
Nov 10 12:45:49 <LetoThe2nd> xtron: the example hello recipe is a recipe that creates a package. the package is called hello
Nov 10 12:45:57 <xtron> LetoThe2nd: but i was following a youtube video and that guy did this, he is not getting this error
Nov 10 12:46:45 <LetoThe2nd> xtron: who says that he did adequately explain all steps?
Nov 10 12:47:02 <LetoThe2nd> xtron: probably he just skipped something and now you are confused.
Nov 10 12:47:16 <open-nandra> hi guys, we heavily use icecc when building yocto
Nov 10 12:47:18 <xtron> LetoThe2nd: ok what is wrong, can you little explain
Nov 10 12:47:32 <LetoThe2nd> xtron: well i am trying to explain it all the time.
Nov 10 12:47:38 <open-nandra> but seems that after bump to krogoth we have random failures which we didn't see previously
Nov 10 12:47:42 <LetoThe2nd> 1) there are recipes that create packages
Nov 10 12:47:48 <LetoThe2nd> 2) there are recipes that create images.
Nov 10 12:48:00 <LetoThe2nd> 3) a recipe that creates an image references a package
Nov 10 12:48:27 <LetoThe2nd> and thats 3(!) different things, but you mangled them into one recipe, and so it breaks.
Nov 10 12:48:51 <LetoThe2nd> xtron: so please, i already told you. create a new layer, start with a fresh hello recipe.
Nov 10 12:48:59 <xtron> LetoThe2nd: but I inherit the core-image, which contain all the info for making image
Nov 10 12:49:56 <xtron> LetoThe2nd: and in bbapend file I define the compile,
Nov 10 12:50:05 <LetoThe2nd> it is still wrong.
Nov 10 12:50:30 <LetoThe2nd> you are mixing up the package creation from the append with the image creation in the recipe itself
Nov 10 12:50:51 <LetoThe2nd> so unless you are not willing to actually try and understand what i am explaining, this becomes rather pointless, sorry.
Nov 10 12:51:35 <xtron> LetoThe2nd: I have done the default stuff and it work but I now this tutorial told me to do this
Nov 10 12:51:51 <LetoThe2nd> then this tutorial is wrong, or you misunderstood it. fact.
Nov 10 12:52:00 <xtron> LetoThe2nd: so what if a want to add hello package, just give me basic idea
Nov 10 12:52:22 <xtron> LetoThe2nd: default layer added,
Nov 10 12:52:42 <xtron> LetoThe2nd: do I need a bbapend file for package inclusion?
Nov 10 12:53:12 <LetoThe2nd> once you have the recipe for the hello package, create an imgae recipe. you can copy core-image-minimal.bb from poky/meta/recipes-core/images to your layer
Nov 10 12:53:26 <LetoThe2nd> rename it maybe to hello-image
Nov 10 12:53:36 <LetoThe2nd> and then in there, add hello to IMAGE_INSTALL
Nov 10 12:55:14 <LetoThe2nd> thats the point. one recipe provides the package, one recipe createsy the image.
Nov 10 12:59:28 <xtron> LetoThe2nd: so that way I've two recipes in my recipes-example ?
Nov 10 12:59:35 <LetoThe2nd> yes.
Nov 10 12:59:56 <LetoThe2nd> again. one recipe provides the package, one recipe creates the image. one and one usually equals two
Nov 10 13:01:12 <xtron> LetoThe2nd: is there anyway to reuse the core-image recipy already available?
Nov 10 13:01:30 <xtron> LetoThe2nd: just inherit it ?
Nov 10 13:02:02 <LetoThe2nd> yes. create an image recipe that inherits core-image
Nov 10 13:02:58 <xtron> LetoThe2nd: one I shared with you is doing this, isn't ?
Nov 10 13:03:41 <LetoThe2nd> yes. thats why i said it is an image recipe
Nov 10 13:03:54 <LetoThe2nd> but you can't just replace the package recipe with it.
Nov 10 13:03:58 <LetoThe2nd> you need both of them
Nov 10 13:05:43 <xtron> LetoThe2nd: ok, thanks
Nov 10 13:06:27 <xtron> LetoThe2nd: thanks for your time
Nov 10 13:07:19 <LetoThe2nd> xtron: hint: stick to the yocto docs, and not to youtube videos. we don't have official ones (yet), and we don't recommend the other ones for a reason.
Nov 10 13:10:50 <xtron> LetoThe2nd: yeah, I tried but .. it sucks :)
Nov 10 13:11:54 <LetoThe2nd> xtron: here, this is as simple as it gets for custom images: https://www.yoctoproject.org/sites/default/files/ypdd-mar2015-intro-lab.pdf
Nov 10 13:16:52 <uglyoldbob> any tips for using devtool on the linux kernel, devtool fails complaining in the Unpacking step, complaining about not a git repository. bitbake works properly on the recipe
Nov 10 13:47:20 <jdmssmkr> Hi, I'm trying to build a custom image and this image should include python3 but I'm getting lot's of errors like "consider defining a PREFERRED_PROVIDER entry to match python-distribute-native". Can't find much information and I'm quite stuck. Anybody with some clues/ideas?
Nov 10 14:05:15 <yocti> New news from stackoverflow: Cannot clone git repo (errno=Connection refused) - ping works <https://stackoverflow.com/questions/47224534/cannot-clone-git-repo-errno-connection-refused-ping-works>
Nov 10 14:08:17 <zero_note> jdmssmkr: seems that you have multiple layers that provides python-distribute-native
Nov 10 14:08:45 <zero_note> uglyoldbob: can you share the errors?
Nov 10 14:10:45 <kanavin> rburton: that's really nice, but I am anxious about mass-refreshing patches like this
Nov 10 14:11:11 <kanavin> rburton: there's no check that the refreshed patch does the right thing, and not just adds/removes code in an incorrect location
Nov 10 14:12:19 <uglyoldbob> zero_note: devtool modify -x linux-gumstix modlin gives "ExecutionError: Execution of 'git --git-dir="/tmp/devtoolGYHNbU/workdir/git" rev-parse HEAD' failed with exit code 128:
Nov 10 14:12:19 <uglyoldbob> fatal: Not a git repository: '/tmp/devtoolGYHNbU/workdir/git'"
Nov 10 14:13:02 <LetoThe2nd> is there more to IMAGE_TYPEDEP? i do have IMAGE_TYPEDEP_ubifs.swu="ubifs", but constructing the ubifs.swu fails because the ubifs file is not ready
Nov 10 14:13:12 <uglyoldbob> zero_note: devtool modify linux-gumstix (place where i already retrieved source) works, but then bitbake linux-gumstix fails with "non-existend task do_shared_workdir"
Nov 10 14:16:02 <LetoThe2nd> listtasks give me do_image_ubifs and do_image_ubifs_swu, where upon direct invocation the former succeeds and the latter fails
Nov 10 14:22:31 <LetoThe2nd> ah dang, DEPLOY_DIR_IMAGE vs. IMGDEPLOYDIR bit me one more time!
Nov 10 14:44:07 <JoiF> nrossi: My u-boot doesn't seem to be using git/board/xilinx/zynq/board.c (i.e. bootmode isn't defined) .. Do you know/remember what determines that?
Nov 10 14:45:01 <JoiF> nrossi: Sorry, "modeboot" is not defined in the environment.
Nov 10 14:46:53 <ranran> Does installing package in ${D}${libdir}  copy the output to package DESTDIR or to rootfs ?
Nov 10 14:53:14 <JoiF> nrossi: Nevermind. I have it now.
Nov 10 15:17:40 <uglyoldbob> does devtool on the kernel normally cause problems with task do_shared_workdir ?
Nov 10 15:21:58 <kergoth> RP: is bitbake -R the best way to examine the configuration metadata of a multiconfig with -e?
Nov 10 15:22:05 <kergoth> haven't done much with multiconfig yet
Nov 10 15:23:07 <ranran> Does installing package in ${D}${libdir}  copy the output to package DESTDIR or to rootfs ?
Nov 10 15:24:15 <kergoth> yes, do_package splits up the content of ${D} into individual packages using PACKAGES and FILES_<pkg>, then the tasks for each packaging method creates binary packages from that
Nov 10 15:24:28 <kergoth> and those packages are then installed into your images based on IMAGE_INSTALL
Nov 10 15:24:43 <kergoth> just adding content to ${D} won't add it to your images alone, however
Nov 10 15:25:40 <ranran> so, is it that the recipe for the image is the one who actually responsible for "collection" the destination packages into rootfs ?
Nov 10 15:26:34 <kergoth> yes, the image recipe controls what packages are installed, directly or indirectly through runtime dependnecies
Nov 10 15:27:20 <ranran> kergoth, thank you, now I got the ideas better.
Nov 10 15:27:27 <kergoth> np
Nov 10 15:27:28 <RP> kergoth: probably, I guess I've not tried to do that before...
Nov 10 15:27:34 <kergoth> RP: k, np.
Nov 10 15:28:58 <kergoth> have a variable using inline python not ending up with the expected value when i bitbake a recipe in the multiconfig, but the -e with -R shows the correct value, trying to diagnose
Nov 10 15:29:00 <kergoth> hmm
Nov 10 15:35:34 <yocti> New news from stackoverflow: VM VirtualBox Network troubles - cannot clone git repos or install nmap <https://stackoverflow.com/questions/47224534/vm-virtualbox-network-troubles-cannot-clone-git-repos-or-install-nmap>
Nov 10 15:43:19 <rburton> any opinions on removing pcmciautils and hostap-utils from oe-core?  not sure when the last laptop with pcmcia was made but it was about the same time that the last prism2 802.11b wifi card was made...
Nov 10 15:50:12 <otavio>   /usr/share/i18n/charmaps/IBM922.gz
Nov 10 15:50:12 <otavio> Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
Nov 10 15:50:15 <otavio> glibc-locale: 828 installed and not shipped files. [installed-vs-shipped]
Nov 10 15:50:22 <otavio> this error is showing in master now
Nov 10 15:50:28 <otavio> is it known?
Nov 10 15:50:42 <rburton> thats a new one
Nov 10 15:50:53 <rburton> does it happen if you wipe tmp and try again?
Nov 10 15:54:25 <otavio> rburton: I am testing it again
Nov 10 15:54:43 <otavio> rburton: I added x11 distro feature (which I don't have on this one)
Nov 10 15:58:11 <ranran> Does anyone knows how to add mirrors in rpm ? My list is empty
Nov 10 15:59:07 <rburton> on target?
Nov 10 15:59:20 <ranran> yes
Nov 10 15:59:40 <ranran> Is it supposed to be empty on first run ?
Nov 10 15:59:43 <rburton> if you set PACKAGE_FEED_URLS in local.conf or whatever to the url where you are hosting the feeds, then the rootfs generation will write the mirror lis
Nov 10 15:59:45 <rburton> t
Nov 10 16:00:00 <rburton> a better question would be: what do you want it set to?
Nov 10 16:00:06 <rburton> it can't know out of the box
Nov 10 16:00:36 <rburton> bitbake doesn't know that i'm running a httpd on port 8080 at /poky-master on a machine called flashheart to set the feed urls
Nov 10 16:00:42 <ranran> Right. Is there a default list that I can use as a start ? I am not familliar with mirrors addresses
Nov 10 16:00:44 <rburton> (well it does now that i set PACKAGE_FEED_URLS)
Nov 10 16:00:56 <rburton> no because its your responsibility to set it up
Nov 10 16:01:17 <rburton> a basic http sharing deploy/rpm will work
Nov 10 16:01:41 <ranran> can you give any example for such http ?
Nov 10 16:01:59 <ranran> I just don't know how to search one.
Nov 10 16:08:04 <ranran> rburton, I also can't find any documentation for PACKAGE_FEED_URLS.
Nov 10 16:09:49 <ranran> maybe it is named PACKAGE_FEED_URIS ?
Nov 10 16:17:13 <fberg> hello guys, I'm new to u-boot. I've manged to run u-boot correctly on a raspberrypi3
Nov 10 16:17:38 <fberg> by the way as now I have only one partition (FAT32 LBA) with the u-boot files only
Nov 10 16:18:01 <fberg> I want to add a second partition on the sd with the kernel image and the rootfs
Nov 10 16:18:29 <fberg> how can I instruct uboot on where to find the kernel.img file ?
Nov 10 16:25:01 <otavio> rburton: I reproduced it; in fact I did use DISTRO_FEATURES =  x11 pulseaudio sysvinit bluez5 gobject-introspection-data ldconfig
Nov 10 17:08:53 <sr105> How do I mask a kernel config fragment in an append recipe?
Nov 10 17:10:04 <sr105> I unset a network module which in turn, made a sub-configuration option disappear. The original recipe has that sub-configuration set which causes kernel_configcheck to show a warning.
Nov 10 17:10:14 <ranran> I am trying to understand where is ${d}
Nov 10 17:11:16 <ranran> It's not the same as rootfs , right ?
Nov 10 17:20:16 <nerdboy> okay, i cleaned up my crufty old config options
Nov 10 17:20:37 <nerdboy> made a systemd image but it stops at  Started udev Coldplug all Devices.
Nov 10 17:21:32 <nerdboy> using the serial console but there's no systemd /etc/init dir for mt serial.conf
Nov 10 17:21:41 <nerdboy> s/mt/my/ even
Nov 10 17:22:04 <nerdboy> what's the "proper" way to add serial console init?
Nov 10 17:31:01 <nerdboy> hmm, looks like systemd-serialgetty is installed but not started
Nov 10 17:57:51 <kdg__> hello, am i (Yocto user) right here with my question regarding lower-case variable d in recipe?
Nov 10 18:01:44 <nerdboy> looks like everything is there under /etc/systemd/system
Nov 10 18:08:41 <kdg__> alsa-lib recipe (meta/recipes-multimedia) uses ${datadir} var set FILES_alsa-conf var. I like to be informed how it resolves.
Nov 10 18:09:39 <kdg__> datadir seems to be set in package_do_split_locales python function, it is done by doing d.getVar('datadir',True)
Nov 10 18:11:16 <kdg__> ${d} seems to be set in recipe_sanity_eh python function, it is done by doing e.data. Here the track breakes. Unfortunately devshell task is not functional if I want to use it for debugging.
Nov 10 18:11:36 <rburton> kdg__: ${datadir} is set in bitbake.conf
Nov 10 18:11:58 <rburton> d is a reference to the datastore, a bb.data instance
Nov 10 18:12:22 <rburton> in python functions inside the classes it is a global
Nov 10 18:14:30 <kdg__> How to see to which value ${d} gets resolved while building alsa-lib?
Nov 10 18:15:48 <ranran> Is there a way to understand where ${D} folder in my system ? Can I see it with devshell ?
Nov 10 18:16:31 <nerdboy> well, same kernel/u-boot works fine with debian stretch :/
Nov 10 18:17:46 <kdg__> ranran: I do it in following way (please double check if proper one): bitbake -e <name of your package or image>  | grep -E '^D='
Nov 10 18:18:47 <ranran> kdg__, thanks! I
Nov 10 18:18:54 <ranran> l shall try it now
Nov 10 18:18:57 <kdg__> raran: Actually in my opinion (please note I am Yocto newbie) should be visible in devshell. However my Yocto/Project does not show several well-known vars in devshell.
Nov 10 18:35:31 <T_UNIX> hm.. it seems that bitbake does not handle simultaneous access to the same repository well...
Nov 10 18:35:34 <sr105> Is it possible to disable a kernel module like Ubuntu's module blacklist file
Nov 10 18:35:35 <sr105> ?
Nov 10 18:58:47 <Guest47029> How do I show all the packages generated from a recipe? Is there a "bitbake recipe-name -c listpkgs" ?
Nov 10 19:26:22 <brianm_> I have a file provided by one package, but it seems to be overridden by some other package
Nov 10 19:26:24 <brianm_> How can I find that other package and make it stop?
Nov 10 19:59:10 <rburton> Guest47029: oe-pkgdata-utils
Nov 10 19:59:56 <Guest47029> rburton: ty!
Nov 10 21:33:58 <sveinse> Is the special patched mkfs.ext4 with the -d option properly tagged runtime, e.g. via. version number. I.e. can I test the version number to identify the -d function, or is this a special yocto-only feature which isn't reflected in the version number of it?
Nov 10 21:35:18 <sveinse> (I'd wish this feature would be available in all versions of mkfs.ext4, not just for Yocto)
Nov 10 21:51:34 <TurBoss> does any one knows when was python 2.7 support for boost was removed?
Nov 10 22:13:03 <mads_> Adding packages to "DEPENDS" does not include their headers/binaries to the recipie specific sysroot
Nov 10 22:13:15 <mads_> yocto version pyro
Nov 10 22:14:26 <neverpanic> It should for headers and libraries, unless your dependency installs them in a nonstandard path
Nov 10 22:14:35 <neverpanic> binaries may be a different story, on the other hand
Nov 10 22:16:24 <mads_> my recipe was compiling on morty with the unified sysroot. But now it fails due to the recipie specific sysroots.
Nov 10 22:19:59 <Crofton|work> mads_, fix the missing DEPENDS
Nov 10 22:20:10 <Crofton|work> mads_, it shoudl
Nov 10 22:23:04 <kergoth> you can't run target binaries, but binaries from -native recipes will be in the native sysroot and the PATH
**** ENDING LOGGING AT Sat Nov 11 03:00:02 2017