**** BEGIN LOGGING AT Thu Feb 19 02:59:58 2015
Feb 19 03:27:01 <Crofton|road> nrossi, gm
Feb 19 03:27:23 <nrossi> morning Crofton
Feb 19 08:03:22 <mckoan> good morning
Feb 19 08:48:01 <JEEBsv> hmm
Feb 19 08:48:13 <JEEBsv> somehow it seems like bitbake isn't finding my distro/hoge.conf
Feb 19 08:49:27 <JEEBsv> layer is added but the thing says it can't find the DISTRO
Feb 19 08:49:55 <JEEBsv> any common pitfalls that I might have fallen into?
Feb 19 08:57:31 * JEEBsv found his issue
Feb 19 09:37:38 <bluelightning> morning all
Feb 19 10:04:32 <tmpsantos> anyone else having linking issues on Ubuntu 14.10?
Feb 19 10:05:02 <tmpsantos> /usr/bin/ld.bfd.real: .libs/sqlite3.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
Feb 19 10:05:12 <tmpsantos> .libs/sqlite3.o: error adding symbols: Bad value
Feb 19 10:05:15 <tmpsantos> like this one ^
Feb 19 10:10:08 <bluelightning> tmpsantos: is this sqlite3-native or sqlite3?
Feb 19 10:12:23 <bluelightning> or indeed nativesdk-sqlite3?
Feb 19 10:15:00 <tmpsantos> bluelightning: native
Feb 19 10:15:31 <tmpsantos> bluelightning: I'm suspecting that ubuntu has some hardening stuff that is messing with yocto
Feb 19 10:18:17 <bluelightning> hmm, I'd not heard of any issues there, but let me give it a try here
Feb 19 10:18:34 <bluelightning> (will need to set up a VM, might take a bit of time)
Feb 19 10:20:38 <tmpsantos> bluelightning: thanks a lot!
Feb 19 10:21:11 <tmpsantos> bluelightning: sorry, the version was 14.04
Feb 19 10:21:51 <tmpsantos> bluelightning: hey, I think I found the issue here
Feb 19 10:22:00 <tmpsantos> has something to do with a custom icecc setup
Feb 19 10:22:15 <bluelightning> oh, ok
Feb 19 10:22:58 <bluelightning> FWIW icecc isn't something we normally test
Feb 19 11:19:38 <milan_> bluelightning: I have a fix to be patched into an inc file. What should be the best way to do it ? (i.e. for bb files we use bbappend, how about inc files ) ?
Feb 19 11:19:53 <bluelightning> milan_: hi
Feb 19 11:20:20 <milan_> hi
Feb 19 11:20:23 <bluelightning> milan_: there is no mechanism to extend included files I'm afraid
Feb 19 11:20:52 <milan_> Does that mean I have to add a bbappend for each bb file ?
Feb 19 11:21:10 <bluelightning> milan_: there are two choices: 1) bbappend all recipes that include the .inc or 2) get a fix into the inc file (which may be adding a variable so that you can select the behaviour you want externally)
Feb 19 11:22:10 <bluelightning> you should also be able to use % as a wildcard in the bbappend name to match more than one recipe
Feb 19 11:22:17 <bluelightning> (in some situations)
Feb 19 11:22:18 <milan_> Ideally it's the second case.
Feb 19 11:23:24 <milan_> bluelightning : Can I see an example of the % approach somehow?
Feb 19 11:23:35 <bluelightning> hmm let me see
Feb 19 11:23:56 <bluelightning> meta-yocto/recipes-core/busybox/busybox_%.bbappend
Feb 19 11:24:24 <milan_> ohh...ok. Let me give this a try .
Feb 19 11:24:45 <milan_> bluelightning : Thank you for the advice :)
Feb 19 11:24:53 <bluelightning> no worries :)
Feb 19 12:42:07 <S_A> Hi
Feb 19 12:42:11 <S_A> Is there some place where I can find latest firefox and WebKit GTK recipe. Is there some reason of maintaining very old versions in git
Feb 19 12:56:22 <S_A> Webkit gtk recipe is 1.8.3 which seems to be too old. Any place to get latest
Feb 19 13:05:17 <JaMa> anyone seen do_rootfs failing with "wfopen: /path/image/2.0-r20/rootfs/etc: Is a directory." recently? I wonder if it's because of globs in CONFFILES
Feb 19 13:07:34 <bluelightning> S_A: AFAIK for webkit-gtk newer versions require ruby to build which we do not have in OE-Core
Feb 19 13:12:33 <S_A> bluelightning: I am not much aware on this but came across http://layers.openembedded.org/layerindex/branch/master/layer/meta-ruby/
Feb 19 13:13:12 <bluelightning> yes, we do have ruby recipes out there, but the issue is OE-Core is supposed to be buildable and testable on its own
Feb 19 13:15:42 <S_A> bluelightning: ok. So is it possible that someone built it & recipe is available at some public location ?
Feb 19 13:15:56 <bluelightning> possibly, but I don't personally know of any
Feb 19 13:16:26 <S_A> bluelightning: ok. Thanks for the info
Feb 19 13:17:07 <S_A> bluelightning: and just out of curiosity. Any specific reason for old build of firefox
Feb 19 13:17:38 <bluelightning> that I don't know... otavio? mario-goulart?
Feb 19 13:20:05 <danielpavel> Hey guys, I'm getting an build error :
Feb 19 13:20:06 <danielpavel> ERROR: Function failed: SYSTEMD_SERVICE_busybox-syslog value busybox-syslog.service does not exist
Feb 19 13:20:23 <danielpavel> can anyone give me a help with this ?
Feb 19 14:12:17 <acidfu> mooo
Feb 19 14:13:02 <acidfu> so the only way to add my layer to BBLAYERS into build/conf/bblayers.conf is manually ? can't it be added automatically when I call ./oe-init-build-env ? thank you !
Feb 19 14:30:49 <bluelightning> acidfu: I guess the question would be how would it know which ones to add?
Feb 19 14:31:22 <acidfu> yes ;)
Feb 19 14:33:01 <bluelightning> FWIW, in master we do now have a command to add layers, although that does just save you the edit
Feb 19 14:33:45 <acidfu> ah ok great
Feb 19 14:43:32 <lpapp> good morning
Feb 19 14:43:37 <lpapp> bluelightning: are you around by any chance
Feb 19 14:43:49 <lpapp> debug busybox does not run on my arm board, but the one from the non-debug package does.
Feb 19 14:44:03 <lpapp> /tmp/busybox
Feb 19 14:44:04 <lpapp> /tmp/busybox: line 1: syntax error: unexpected word (expecting ")")
Feb 19 14:44:12 <lpapp> this is for the one from the -dbg package (dylan).
Feb 19 14:44:51 <lpapp> LD_TRACE_LOADED_OBJECTS=1 /tmp/busybox says the interpreter is the same as for the non-debug version, so that looks alright to me.
Feb 19 14:45:15 <lpapp> file says this: busybox/1.20.2-r11/packages-split/busybox-dbg/bin/.debug/busybox: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=0x84da43ebb8eb9bb605a444d996af4ad2a467da8b, not stripped
Feb 19 14:45:34 <bluelightning> hi lpapp
Feb 19 14:45:37 <lpapp> perhaps I am not supposed to run that file directly? If so, how am I?
Feb 19 14:45:40 <bluelightning> hmm, not sure about that...
Feb 19 14:46:07 <bluelightning> is that with our default debug setup or did you customise how those packages are created? I recall we talked about how the default didn't work in your situation
Feb 19 14:46:28 <lpapp> I have a custom patch, so I am using .bbappend in my layer.
Feb 19 14:46:37 <lpapp> I also enabled debug with bitbake -c menuconfig busybox
Feb 19 14:46:42 <lpapp> and then bitbake busybox
Feb 19 14:46:57 <lpapp> busybox does not have a "debug" target in the buildsystem as it is using the kernel's configuration system
Feb 19 14:47:28 <lpapp> I can verify it with stock busybox from meta/recipes-core
Feb 19 14:47:40 <lpapp> (if I can tell Yocto to build it from there, somehow
Feb 19 14:47:42 <lpapp> )
Feb 19 14:47:52 <lpapp> in worst case, I can remove my directory temporarily.
Feb 19 14:48:16 <lpapp> oh, I remember, sort of.
Feb 19 14:48:26 <lpapp> .debug/foo is just the symbols, it is not the executable, I think
Feb 19 14:48:32 <lpapp> so it is only valid with the main.
Feb 19 14:48:34 <lpapp> (together)
Feb 19 15:06:15 <tmpsantos> bluelightning: we found the issue here, the ubuntu box had the package "hardening-wrapper" installed
Feb 19 15:06:30 <tmpsantos> this is a compiler wrapper that adds some funny security flags
Feb 19 15:07:29 <bluelightning> tmpsantos: ah ok, interesting... I wonder if we should do anything about that
Feb 19 15:07:44 <tmpsantos> bluelightning: we could have maybe a package blacklist
Feb 19 15:08:18 <tmpsantos> and warn the user if he/she has one of the packages in the blacklist installed in the system
Feb 19 15:08:44 <bluelightning> we certainly have sanity checks for similar configurations that will break the build system
Feb 19 15:09:12 <bluelightning> unfortunately those checks are usually only run once on first build, they don't retrigger when people install new packages on the build host
Feb 19 15:09:17 <bluelightning> which is not ideal
Feb 19 15:54:21 <ulf`> Hi
Feb 19 15:58:42 <ulf`> Hi pidge ;)
Feb 19 16:03:56 <pidge> waves to ulf`
Feb 19 16:28:59 <ericbutters> hello, anyone got problems today with meta-openembedded fetching?
Feb 19 16:30:28 <Lern-X> Hello, is a "Function failed : do_prep" error a meta-openembedded fetching problem ?
Feb 19 16:30:30 <onoffon> ericbutters I hope you are not fetching from oe.git
Feb 19 16:30:45 <onoffon> you should use github mirror
Feb 19 16:31:15 <onoffon> no do_prep is a task for some package thats failing for you
Feb 19 16:31:20 <ericbutters> git://git.openembedded.org
Feb 19 16:31:38 <onoffon> ericbutters its recommended to use github
Feb 19 16:31:56 <ericbutters> okay thanks
Feb 19 16:32:11 <Lern-X> onoffon: do you know if it's bugging because of my distro (Fedora21) ?
Feb 19 16:32:20 <onoffon> https://github.com/openembedded
Feb 19 16:32:52 <onoffon> Lern-X I dont know you havent given info to assert that
Feb 19 16:33:38 <Lern-X> onoffon: okay, i'm going to explain :)
Feb 19 16:34:10 <Lern-X> So I want to build a Tizen image (more precisely, a tizen-common-core-image-minimal-dev one), using Yocto.
Feb 19 16:34:24 <Lern-X> So I typed these commands :
Feb 19 16:34:26 <Lern-X> git clone git://review.tizen.org/scm/bb/tizen-distro
Feb 19 16:34:42 <Lern-X>  cd tizen-distro; git checkout tizen;
Feb 19 16:34:48 <Lern-X> build_directory_name=build-common;
Feb 19 16:35:00 <Lern-X> and :
Feb 19 16:35:34 <Lern-X> source ./tizen-common-int-build-env thebuilddirect
Feb 19 16:35:43 <Lern-X> I didn't modify the local conf.
Feb 19 16:35:53 <bluelightning> do_prep is definitely a task that meta-tizen has defined, it's not something standard
Feb 19 16:36:03 <bluelightning> did you get anywhere asking about this on their mailing lists?
Feb 19 16:36:19 <Lern-X> I sent a message to yocto list
Feb 19 16:36:33 <Lern-X> I should send it to the tizen's one ?
Feb 19 16:36:44 <bluelightning> that's what I was suggesting yesterday yes
Feb 19 16:37:32 <Lern-X> Okay, i'll do it so, thanks,
Feb 19 16:40:21 <ericbutters> bluelightning: onoffon: i use this manifest for repo tool: http://paste.ubuntu.com/10310374/ but i get: error: Cannot fetch meta-openembedded
Feb 19 16:40:48 <ericbutters> i used to fetch git://git.openembedded.org and that worked until today..
Feb 19 16:41:08 <ericbutters> now with github i get fetch error
Feb 19 16:41:21 <onoffon> well you need to use meta-openembedded repo
Feb 19 16:41:26 <onoffon> openembedded is old OE
Feb 19 16:41:51 <bluelightning> FWIW, git clone works fine for me just now on  git://git.openembedded.org/meta-openembedded ...
Feb 19 16:52:22 <ericbutters> bluelightning: yes that works.. it is kind of strange.. 10% of the cases it works for me with repo also. i think that is a problem with my network here.. or the openembedded server. i am going to try tomorrow again ;)
Feb 19 16:56:52 <bluelightning> ericbutters: it could be at either end, or an issue somewhere between
Feb 19 16:57:07 <bluelightning> ericbutters: if it persists by all means let us know
Feb 19 19:39:43 <oskude> hi, is there a bottom-up tutorial for yocto? like i would like to know how to create a minimal image that only has a filesystem, bootloader and linux kernel. then start adding init system and so on.
Feb 19 19:58:12 <WarheadsSE> hmm
Feb 19 19:58:43 <WarheadsSE> you'll need the basics, and look into how image recipes work
Feb 19 19:58:57 <WarheadsSE> Can't speak to a turotial for that exact path though
Feb 19 20:04:44 <oskude> yeah, been trying to learn top-down from core-image-minimal but the rabbit hole just keeps going, and branching :/
Feb 19 20:05:42 <WarheadsSE> heh
Feb 19 20:15:53 <oskude> stupid question, what are the git tags yocto-1.7.1 and dizzy-12.0.1? they both point to the same commit?
Feb 19 20:22:28 <WarheadsSE> because they are the same
Feb 19 20:23:04 <WarheadsSE> yocto (the system) 1.7.1 _is_ dizzy (layer set named version) 12.0.1
Feb 19 20:25:18 <fray> Poky has existed since before the Yocto Project..
Feb 19 20:25:30 <fray> it's up to version 12.., which happens to match the Yocto Project version 1.7
Feb 19 20:25:42 <fray> and dizzy is the code name for that release..
Feb 19 20:25:51 <fray> so..  dizzy == YP 1.7 == Poky 12
Feb 19 20:26:19 <oskude> so many names :/
Feb 19 20:26:27 <oskude> but i think i slowly get it
Feb 19 20:27:10 <WarheadsSE> the nature of merging and re-org'ing projects. It happens
Feb 19 21:31:15 <acidfu> does bitbake rescan all the possible recipes every time I do "bitbake image" ?
Feb 19 21:31:17 <acidfu> thx
Feb 19 21:31:28 <WarheadsSE> yes
**** ENDING LOGGING AT Fri Feb 20 02:59:59 2015