**** BEGIN LOGGING AT Sun Sep 25 02:59:59 2016
Sep 25 06:13:59 <mfny> hi all
Sep 25 07:06:21 <lukma> bluelightning: Thanks for answer
Sep 25 07:06:30 <lukma> The problem is that this is not the ordinary image
Sep 25 07:06:42 <lukma> it is supposed to be on the SD card
Sep 25 07:25:35 <mfny> anyone here ?
Sep 25 07:30:17 <mfny> cant get yocto to build with x11 at all
Sep 25 08:25:16 <mfny> bluelightning:  you here ?
Sep 25 08:25:40 <bluelightning> mfny: kind of
Sep 25 08:26:09 <mfny> still cant get that x11 config error to clear
Sep 25 08:26:24 <mfny> getting realy flustrating
Sep 25 08:27:13 <Ulfalizer> mfny: unrelated, but just to save you some future embarrassment: it is spelled "frustrating" :)
Sep 25 08:27:45 <bluelightning> mfny: did you try what I suggested?
Sep 25 08:27:47 <Snert> Retaed with frust lol
Sep 25 08:27:59 <Snert> I hate those erros
Sep 25 08:28:41 <mfny> bluelightning: i didnt see your surgestion ..
Sep 25 08:29:00 <mfny> Ulfalizer: my spelling isnt great, deal with it :)
Sep 25 08:29:38 <bluelightning> mfny: try deleting the bbappend from meta-xilinx (or renaming to e.g. .bbappend_disabled)
Sep 25 08:33:59 <mfny> thats makeing it do the rootfs so so far so good
Sep 25 08:34:33 <mfny> and build is done
Sep 25 08:34:54 <mfny> now to see if it will work
Sep 25 08:35:22 <mfny> hopefully x11 will just generate its own config
Sep 25 08:35:40 <mfny> or if not i can copy those config files manualy i guess
Sep 25 08:50:03 <mfny> yay, it works
Sep 25 08:50:09 <mfny> bluelightning:  thanks
Sep 25 08:50:31 <bluelightning> mfny: no problem
Sep 25 08:50:44 <bluelightning> mfny: you should probably tell the meta-xilinx maintainer to fix their broken bbappend
Sep 25 08:50:49 <bluelightning> (or fix it for them and send a patch)
Sep 25 08:51:27 <mfny> im a noob so fixing it for them is outside of my skill set
Sep 25 08:52:19 <mfny> bluelightning: im just getting started with FPGAs
Sep 25 08:53:46 <mfny> hm is there a standard x11 image with something more PC like then Sato ?
Sep 25 08:54:15 <mfny> like a proper WM
Sep 25 08:56:35 <bluelightning> mfny: you could always add meta-xfce, I believe that provides a reasonable starting image
Sep 25 08:57:35 <mfny> how would i get the xfce image built ?
Sep 25 08:57:47 <mfny> i think ive tried it and it didnt work
Sep 25 08:58:54 <mfny> ah i get this
Sep 25 08:58:58 <mfny> ERROR: Nothing PROVIDES 'core-image-minimal-xfce'. Close matches:   core-image-minimal-dev   core-image-minimal   core-image-minimal-initramfs
Sep 25 09:13:15 <mfny> bluelightning: any ideas for that ?
Sep 25 09:19:43 <bluelightning> mfny: have you added meta-xfce to your configuration?
Sep 25 09:21:36 <mfny> no, how would i do that ?
Sep 25 09:33:23 <bluelightning> mfny: here's the layer: https://layers.openembedded.org/layerindex/branch/master/layer/meta-xfce/
Sep 25 09:33:44 <bluelightning> you're going to need to clone that and the listed dependencies, then add the paths to conf/bblayers.conf
Sep 25 09:33:48 <mfny> im working out how to add layers now.. think i have it
Sep 25 09:37:51 <mfny> bluelightning: building now :)
Sep 25 09:40:09 <mfny> bluelightning: what platform(s) do you run yocto on ?
Sep 25 09:40:44 <bluelightning> mfny: well, I'm one of the developers so I test it on all sorts of different platforms
Sep 25 09:41:48 <mfny> bluelightning: ohh your a dev, didnt know that
Sep 25 09:42:41 <mfny> bluelightning: im running on a Zybo (Xilinx Zynq 7010) board
Sep 25 09:42:55 <mfny> bluelightning: its a nice board so far
Sep 25 09:43:29 <mfny> bluelightning: also yocto building could be easier... just saying :)
Sep 25 09:44:04 <bluelightning> mfny: well, you've hit bugs, that shouldn't happen
Sep 25 09:44:18 <bluelightning> mfny: but there are easier ways to build, e.g. Toaster
Sep 25 09:44:42 <bluelightning> there's even a docker container for Toaster now so it's just a few commands to set up
Sep 25 09:45:02 <mfny> oh there is a docker ? neat
Sep 25 09:45:14 <mfny> may have to look into that
Sep 25 09:47:33 <bluelightning> https://github.com/crops/toaster-container
Sep 25 10:15:50 <mfny> bluelightning: that xfce minimal image works fine :)
Sep 25 10:37:05 <bluelightning> mfny: cool
Sep 25 10:40:49 <auke-> Hi! I'm trying to revive my custom Yocto image based on Jethro with a clean build, but gcc-cross-initial-arm fails to compile (undefined reference to expand_shift, see http://pastebin.com/Kg1sHjgW). What could cause this error?
Sep 25 18:05:14 <lukma> Dear All,
Sep 25 18:05:31 <lukma> Is there a way to get ${LAYERDIR} in the recipie ?
Sep 25 18:05:57 <kergoth> bitbake doesn't keep track of what layer a given recipe lives in, but you can determine it after  the fact in the metadata
Sep 25 18:06:20 <lukma> I have my own layer -> meta-mylayer
Sep 25 18:06:42 <lukma> and I plan to store shared file at meta-mylayer/conf
Sep 25 18:07:03 <lukma> (or maybe I shall create meta-mylayer/recipie-common ) ?
Sep 25 18:07:31 <lukma> I want to share one file between recipies in different directories
Sep 25 18:08:11 <kergoth> depends on what it is. you could include a file from each recipe, or use a class and inherit it, or load a config file globally from local.conf
Sep 25 18:09:03 <lukma> How can I load it globally from local.conf
Sep 25 18:09:14 <kergoth> there's no need to know the path to the layer to include a file, though
Sep 25 18:09:29 <kergoth> if you use a relative path to 'include' or 'require', it'll search BBPATH, which searches the layers, for that path relative to the top of the layer
Sep 25 18:09:30 <lukma> It is a simple text file with few lines in it
Sep 25 18:09:43 <kergoth> include conf/foo.conf will find foo.conf in your layer
Sep 25 18:09:45 <kergoth> for example
Sep 25 18:09:52 <lukma> aaaaa
Sep 25 18:10:03 <kergoth> it's how all config files and classes are found
Sep 25 18:10:15 <lukma> so I can include everyfile which was added to BBPATH during configuration?
Sep 25 18:10:17 <kergoth> i.e. bitbake.conf does include conf/local.conf, that's how local.conf is found. the build dir & the layer dirs are in bbpath
Sep 25 18:10:22 <kergoth> that doesn't make sense
Sep 25 18:10:28 <kergoth> bbpath lists directories, much like PATH
Sep 25 18:10:41 <kergoth> it's a search path, used to find specific files
Sep 25 18:10:47 <lukma> so I can add "include conf/my_file.txt" in the recipie which needs it?
Sep 25 18:10:54 <kergoth> yes
Sep 25 18:10:56 <kergoth> though .txt is invalid
Sep 25 18:12:06 <lukma> ERROR: ParseError in "conf/fw_env.config": not a BitBake file
Sep 25 18:12:32 <kergoth> yes, include/require are used to include bitbake config files
Sep 25 18:12:56 <kergoth> if it's a file you want to include source wise, it's still doable, but slightly more complex
Sep 25 18:13:24 <lukma> So to present what I'm trying to solve here:
Sep 25 18:13:43 <kergoth> SRC_URI += "file://fw_env.config"; FILESPATH .= ":${@os.path.dirname(bb.utils.which('${BBPATH}', 'conf/fw_env.config'))}"
Sep 25 18:14:00 <kergoth> would search the layers for the file, get the dir name of that, then add that to the seach path for file:// files
Sep 25 18:14:03 <kergoth> that's one option
Sep 25 18:16:19 <lukma> kergoth: why I extend FILESPATH after add add SRC_URI ?
Sep 25 18:19:29 <lukma> Still no luck
Sep 25 18:19:31 <lukma> ${@os.path.dirname(bb.utils.which('${BBPATH}', 'conf/fw_env.config'))}"
Sep 25 18:19:36 <lukma> FILESEXTRAPATHS_prepend := ":${@os.path.dirname(bb.utils.which('${BBPATH}', 'conf/fw_env.config'))}"
Sep 25 18:19:36 <lukma> SRC_URI += "file://fw_env.config"
Sep 25 18:19:48 <lukma> I've modified it a bit since the original version was also not working
Sep 25 18:23:40 <kergoth> you're prepending, but didn't move the : separator
Sep 25 18:23:51 <kergoth> if you prepend, the separator has to be at the end, not the beginning
Sep 25 18:24:03 <kergoth> otherwise you'll get a result like :foobar instead of foo:bar
Sep 25 18:24:36 <kergoth> and order is irrelevent, it doesn't matter what order thet wo variables are defined in, bitbake doesn't use their values until long after they're parsed
Sep 25 18:26:20 <kergoth> afk
Sep 25 18:26:29 <lukma> kergoth: Yes you are right
Sep 25 18:26:39 <lukma> the colon was in wrong place
Sep 25 18:26:55 <lukma> and I think that FILESETEXTRAPATHS is the way to add this
Sep 25 18:26:57 <lukma> :)
Sep 25 18:28:27 <lukma>  kergoth: And If I may
Sep 25 18:28:55 <lukma> Is there a way to see only the list of tasks executed for a recipie? (-n? -g?)
Sep 25 18:41:11 <lukma> kergoth: And one more question
Sep 25 18:42:00 <lukma> how can I access this fw_env.config when I write my own do_populate_rootfs() @ *.bbappen ?
Sep 25 18:42:11 <lukma> Is it accessible with ${S} ?
Sep 25 18:42:22 <lukma> (with ${S} it is not working)
Sep 25 18:47:01 <kergoth> file:// files in SRC_URI are unpacked to WORKDIR, not S
Sep 25 18:53:29 <lukma> with {WORKDIR} it also shows that the file is not found
Sep 25 18:54:16 <Ulfalizer> haven't really followed the discussion, but a nice debugging technique is to search for it in the build directory and then trying to correlate that to variables
Sep 25 18:54:29 <Ulfalizer> that way you'll get a feel for the layout as well
Sep 25 18:54:49 <Ulfalizer> the ${WORKDIR}s for recipes are in the build directory
Sep 25 18:54:50 <lukma> But when I search for it:
Sep 25 18:57:20 <lukma> http://pastebin.com/ugntt6Cu
Sep 25 18:57:31 <lukma> there is no fw_env.config
Sep 25 18:58:09 <lukma> find also is not showing anything
Sep 25 19:02:37 <Ulfalizer> lukma: does the do_fetch task for the recipe run without errors?
Sep 25 19:02:52 <Ulfalizer> that's the one that'll copy that file into WORKDIR
Sep 25 19:03:25 <Ulfalizer> also, make sure that you're not overriding SRC_URI with a = after your +=. check the output of bitbake -e to see the final value of SRC_URI.
Sep 25 19:04:13 <Ulfalizer> version 2.2 of the reference manual has more details on bitbake -e btw
Sep 25 19:04:23 <Ulfalizer> compared to earlier versions
Sep 25 19:07:14 * Ulfalizer gets food
Sep 25 19:22:32 <lukma> hmmm
Sep 25 19:28:20 <lukma> do_fetch went smooth
Sep 25 19:52:11 <lukma> ok, the "hackish" solution -> I've installed the original package which was installing this file
Sep 25 19:52:22 <lukma> in the image, which I needed :D
Sep 25 19:52:44 <lukma> Oneliner with .bbappend
**** ENDING LOGGING AT Mon Sep 26 02:59:58 2016