**** BEGIN LOGGING AT Mon Dec 09 02:59:58 2013
Dec 09 06:36:11 <newbie101> hello..i'm new to yocto..i have problem building 3rd party library..i'm having libtool mismatch..
Dec 09 07:21:17 <oswin> Hi all, I'm beginning with Yocto, and would like to know what is the difference between a yocto poky and an oe git tree ?
Dec 09 08:30:19 <ak77> hello.
Dec 09 08:31:06 <ak77> is there a task to mount produced rootfs for inspection?
Dec 09 08:34:51 <ak77> answer: no, as it is simple as "mount -o loop rootfs.img /mnt/rootfs"
Dec 09 08:45:39 <B4gder> https://wiki.yoctoproject.org/wiki/Security is a bit sad ...
Dec 09 09:38:46 <rburton> ak77: the work directory for the rootfs also has the file system before it was actually in a standalone filesystem
Dec 09 09:57:54 <bluelightning> morning all
Dec 09 10:09:55 <LetoThe2nd> howdy! is there any support for working with poky on a nfs root? first try broke because of not being able to create hard links. :(
Dec 09 10:21:59 <oswin> LetoThe2nd, nfs root worked fine for me out of box
Dec 09 10:23:54 <LetoThe2nd> oswin: hm ok
Dec 09 10:24:24 <oswin> LetoThe2nd, wich target did you build ?
Dec 09 10:38:33 <LetoThe2nd> oswin: it was not myself, coworker reported it. he said he tried to follow https://www.yoctoproject.org/download/texas-instruments-arm-cortex-a8-development-board-beagleboard-3
Dec 09 10:38:41 <LetoThe2nd> nut doesn't have more details at hand reight now
Dec 09 12:15:20 <Ramose> How do I make a particular file readonly in rootfs image?
Dec 09 12:16:32 <oswin> with fs file permission. Better would be to mount another file system in ro
Dec 09 12:18:07 <Ramose> oswin: I didn't get you
Dec 09 12:18:20 <Ramose> could you explain your point a bit
Dec 09 12:24:35 <oswin> you can create a new image/partition with the files you want to be RO, then you mount this image/partition in your rootfs in RO, it will guarantee your files could not be accessible in write mode
Dec 09 12:25:08 <rburton> unless someone has root and can re-mounted the fs
Dec 09 12:25:35 <B4gder> why is a ro-fs better than just a ro-file for a single file?
Dec 09 12:25:40 <B4gder> seems overly complicated
Dec 09 12:30:29 <Ramose> oswin: Can I use IMAGE_FEATURES for my purpose?
Dec 09 12:30:54 <rburton> Ramose: just chmod the file if you want to make it read-only
Dec 09 12:31:17 <rburton> (and then don't run anything as root if you actually want it to stay read only)
Dec 09 12:31:32 <rburton> well, chmod+chown.
Dec 09 12:32:49 <oswin> B4gder, it's not technically safer, but it avoid to accidentally changes rights of a file as you work on your roots
Dec 09 12:33:05 <B4gder> accidentally run as root and do chmod?
Dec 09 12:33:06 <Ramose> rburton: I tried doing it by iinstall -m 444 ${WORKDIR}/sshd_config ${D}${sysconfdir}/ssh/sshd_config
Dec 09 12:33:19 <Ramose> but it didn't work out for me
Dec 09 12:33:32 <Ramose> sshd_config file i wanted to make read only
Dec 09 12:34:09 <rburton> Ramose: if you're making that read only are you also stopping someone from providing their own sshdconfig and starting sshd themselves? the point being, what are you actually trying to stop?
Dec 09 12:34:27 <rburton> (one better idea would be read-only rootfs)
Dec 09 12:36:49 <Ramose> i don't want it to modify by someoen who don't root permission
Dec 09 12:37:22 <rburton> Ramose: by default its 644, so its only writable by root
Dec 09 12:37:33 <Ramose> <rburton> (one better idea would be read-only rootfs) ,wouldn't it make every file readonly in rootfs?
Dec 09 12:37:43 <rburton> yes, a read only rootfs has every file read-only.
Dec 09 12:37:57 <rburton> you then mount read-write bits where you need them
Dec 09 12:39:28 <rburton> -rw-r--r-- 2 ross ross   3277 Dec  9 12:38 sshd_config <-- ignore ross/ross, this is my work tree.
Dec 09 12:43:52 <Ramose> rburton: Can't we override default permission 644 to 444 using linux install command?
Dec 09 12:44:07 <rburton> you probably can, but root can just chmod it back again
Dec 09 12:44:12 <rburton> so you're not gaining anything there
Dec 09 12:45:36 <Ramose> right rburton ,got your point but i am not Worrying about "root can just chmod it back again"
Dec 09 12:45:55 <Ramose> i just want to show the file permission to 444 at first place
Dec 09 12:46:53 <rburton> then a chmod should work, yes.
Dec 09 12:48:02 <Ramose> ok i have added this chmod 444 ${WORKDIR}/sshd_config ${D}${sysconfdir}/ssh/sshd_config
Dec 09 12:48:05 <Ramose> would it be fine
Dec 09 12:48:38 <rburton> you don't need the workdir bit, and do it in the do_install_append
Dec 09 12:49:01 <rburton> still no point to this though ;)
Dec 09 12:49:08 * rburton -> run, third time lucky
Dec 09 12:49:33 <Ramose> yes rburton it looks very odd requirement to me as well
Dec 09 13:11:18 <Ramose> running out of luck ,added this line under do_install_append chmod 444 ${WORKDIR}/sshd_config ${D}${sysconfdir}/ssh/sshd_config ,but under rootfs's /etc/ssh file permission is still 444
Dec 09 13:18:50 <Zaif> There are two recipes of dhcp in meta and meta-openembedded. When I append dhcp in my image file, which one does bitbake choose?
Dec 09 13:23:03 <Ramose> Zaif: Do your recipe have some PV?
Dec 09 13:24:56 <bluelightning> Zaif: there is no dhcp recipe in meta-openembedded as far as I can tell...
Dec 09 13:27:13 <Ramose> * running out of luck ,added this line under do_install_append chmod 444 ${WORKDIR}/sshd_config ${D}${sysconfdir}/ssh/sshd_config ,but under rootfs's /etc/ssh file permission is still 644
Dec 09 13:28:13 <Zaif> Ramose: dhcp meta has 4.2.5 with PR=r1, and when I check in /work, the dhcp downloaded was 4.2.3-r3.
Dec 09 13:29:54 <Ramose> Zaif ,do dhcp recipe of meta-openembedded have version 4.2.3?
Dec 09 13:32:11 <Zaif> Ramose: In meta-openembedded there is a dhcp_4.2.5.bbappend file
Dec 09 13:33:00 <Zaif> bluelightning: It was a slight confusion, yes there is no dhcp recipe in meta-openembedded, but some .bbappend file.
Dec 09 13:34:08 <Zaif> bluelightning, Ramose: When I append dhcp in my image, I get, dhcp not found in base feeds error http://pastebin.com/LnWqsL5T
Dec 09 13:34:28 <Zaif> an idea, why bitbake is generating this error?
Dec 09 13:40:39 <bluelightning> Zaif: the "dhcp" package is empty and thus is never produced
Dec 09 13:41:13 <bluelightning> Zaif: you need to install one of the other packages it produces, such as dhcp-client or dhcp-server (depending on what you want)
Dec 09 13:46:02 <Zaif> bluelightning: Ok. Will include specific packages and build again.
Dec 09 14:35:16 <oswin> where does HOB store his config about chosen packages ?
Dec 09 14:38:24 <Ramose> I have added ip neighbour recipe and did IMAGE-INSTALL += "ip neighbour"
Dec 09 14:38:39 <Ramose> but when I do bitbake ip neighbour
Dec 09 14:39:00 <Ramose> gets error :Nothing proivides ip neighbour
Dec 09 14:39:07 <belen> oswin: if I am understanding your question correctly, the answer might be nowhere, I am afraid
Dec 09 14:39:37 <Ramose> can anyone point me what I am doing wrong
Dec 09 14:40:27 <belen> oswin: after completing your build, if you have modified the package list for the standard image recipe, you can save your changes as a new image recipe. That would be a way of keeping your package selections, I guess
Dec 09 14:41:11 <bluelightning> Ramose: your recipe doesn't have a space in its name does it?
Dec 09 14:43:00 <bluelightning> Ramose: if so, that's not allowed I'm afraid, you'd need to use - instead (not _, that's only allowed for separating the name and version in a recipe file name)
Dec 09 14:43:02 <Ramose> bluelightning: it doesn't have space
Dec 09 14:43:18 <bluelightning> Ramose: so what is your recipe called?
Dec 09 14:45:08 <Ramose> ipneighbour
Dec 09 14:45:44 <oswin> belen, ok, so I have to save it before closing HOB ? What is the "standard image receipe" ? The one associated to the image I built or the one in meta-hob ?
Dec 09 14:45:52 <Ramose> bluelightning: One point here what ever Iput againts IMAGE-INSTALL is should be recipe name?
Dec 09 14:46:55 <bluelightning> Ramose: IMAGE_INSTALL accepts package names, not recipe names; but in most cases the main package for a recipe has the same name as the recipe
Dec 09 14:47:10 <drasko> HI all, I am getting: ERROR: QA Issue: No GNU_HASH in the elf binary
Dec 09 14:50:49 <Ramose> bluelightning: Looks like my recipe started getting bitbake
Dec 09 14:51:01 <Ramose> getting this error though ,Recipe file does not have license file information (LIC_FILES_CHKSUM)
Dec 09 14:51:20 <bluelightning> Ramose: if it's the "ip neighbour" command that you want, I think maybe you just need to install iproute2
Dec 09 14:51:33 <bluelightning> which we already have a recipe for
Dec 09 14:54:30 <Ramose> ok bluelightning but how Do I tackle Recipe file does not have license file information (LIC_FILES_CHKSUM) error
Dec 09 14:54:53 <Ramose> i just checked LIC_FILES_CHKSUM is missing from my recipe
Dec 09 14:55:10 <Ramose> where Do I get LIC_FILES_CHKSUM for my recipe
Dec 09 14:55:17 <bluelightning> Ramose: this is where I point you to the manual ;) http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-LIC_FILES_CHKSUM
Dec 09 14:56:51 <Ramose> Thanks bluelightning
Dec 09 15:04:33 <Ramose> bluelightning: setting the LICENSE to closed worked for me
Dec 09 15:05:10 <Ramose> but is it safe to set LICENSE to closed
Dec 09 15:05:10 <Ramose> ?
Dec 09 15:05:45 <vicenteolivert> Hello.
Dec 09 15:07:10 <bluelightning> Ramose: only if that's really the right value, if it's not a closed-source piece of software that is not appropriate
Dec 09 15:07:14 <vicenteolivert> I was reading the documentation, specifically the "1.3.1. Supported Linux Distributions" paragraph, and it tells that CentOS 6.4 is supported, but I have CentOS 6.4 and the first problem I face with is:
Dec 09 15:07:17 <vicenteolivert> BitBake requires Python 2.7.3 or later
Dec 09 15:07:38 <vicenteolivert> The is no Python 2.7 on CentOS 6.4
Dec 09 15:07:59 <bluelightning> vicenteolivert: right, CentOS 6 does not provide a new enough version of python, but we provide buildtools-tarball that includes 2.7.3
Dec 09 15:08:37 <vicenteolivert> bluelightning: oh, so I need to read about the buildtools-tarball. Thank you :-)
Dec 09 15:09:05 <bluelightning> vicenteolivert: the quick start guide links to here: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#required-git-tar-and-python-versions
Dec 09 15:10:13 <vicenteolivert> bluelightning: thank you.
Dec 09 15:10:56 <mckoan> otavio: today I can't fetch from git://git.freescale.com using Yocto, doing it manually with git clone works. Any clue?
Dec 09 15:12:05 <mckoan> maybe is my network too slow today
Dec 09 15:27:37 <vicenteolivert> bluelightning: does that buildtools-tarball contains everything I need to work with Yocto?
Dec 09 15:38:04 <bluelightning> vicenteolivert: it contains appropriate python, git and tar versions that your distro may not provide new enough versions of, however you still need to install some packages on your host system (as listed in the quick start guide)
Dec 09 15:40:51 <vicenteolivert> bluelightning: yes, sorry , I realized that was a silly question.
Dec 09 15:41:16 <bluelightning> vicenteolivert: no worries, there are no silly questions ;)
Dec 09 15:41:35 <vicenteolivert> :-) Thanks.
Dec 09 16:29:25 <_tid> hello, i'm trying to write a recipe for "pacpaser" https://code.google.com/p/pacparser/downloads/detail?name=pacparser-1.3.1.tar.gz
Dec 09 16:29:34 <_tid> it fail because the build is strange, the setup.py need a lib to be compiled first
Dec 09 16:29:45 <_tid> and the compilation use gcc instead of the arm cc
Dec 09 16:29:57 <_tid> so it fail with Relocations in generic ELF or libjs.a: could not read symbols: File in wrong format
Dec 09 16:30:24 <_tid> the make file use $(CC) so i don't know what to fix :)
Dec 09 16:55:02 <bluelightning> _tid: is the makefile also setting a value for CC perhaps?
Dec 09 16:55:35 <_tid> i'm look for that, but i've only found $CC
Dec 09 16:56:33 <bluelightning> _tid: your recipe isn't doing "inherit native" or anything like that is it?
Dec 09 16:57:10 <_tid> not it's the standard python i've used for other py ext inherit distutils pythonnative
Dec 09 16:57:32 <_tid> pythonnative is a bad idea ?
Dec 09 16:57:38 <bluelightning> no, that should be fine
Dec 09 16:58:02 <bluelightning> can you see which compiler it's using in log.do_compile ?
Dec 09 16:58:05 <_tid> gcc
Dec 09 16:58:38 <_tid> gcc -o Linux_All_DBG.OBJ/jsapi.o -c -fPIC -DHAVE_VA_COPY -DVA_COPY=__va_copy -Wall -Wno-format -g -DXP_UNIX -DSVR4 -DSYSV -D_BSD_SOURCE -DPOSIX_SOURCE -DHAVE_LOCALTIME_R -DX86_LINUX  -DDEBUG -DDEBUG_yoctodev -DEDITLINE -ILinux_All_DBG.OBJ  jsapi.c
Dec 09 16:59:55 <bluelightning> _tid: hmm... maybe try EXTRA_OEMAKE = "'CC=${CC}'
Dec 09 17:00:21 <_tid> hum let's try
Dec 09 17:00:50 <_tid> some part of the compile use gcc some other the good one arm-poky...
Dec 09 17:04:35 <_tid> no luck with EXTRA_OEMAKE
Dec 09 17:04:43 <bluelightning> that kind of sounds like CC is not being used in some places
Dec 09 17:04:50 <_tid> true
Dec 09 17:05:00 <_tid> but i can't find where, this pacparser is strange :)
Dec 09 17:06:07 <_tid> there is a thing like that : CFLAGS="$(SMCFLAGS)" $(MAKE) -C js/src -f Makefile.ref libjs.a
Dec 09 17:07:56 <bluelightning> _tid: maybe the issue is in the makefile in the embedded copy of js?
Dec 09 17:08:16 <_tid> you are probably right :)
Dec 09 17:08:21 <bluelightning> there is a tarball of it in the git repo, but it's not entirely clear to me how that gets extracted
Dec 09 17:11:24 <_tid> hum.. some makefile magic make it appears extracted :)
Dec 09 17:11:50 <_tid> in src/spidermonkey/js/src
Dec 09 17:15:05 <_tid> it's probably in src/spidermonkey/js/src/Makefile.in
Dec 09 17:17:01 <_tid> hum found it config/Linux_All.mk
Dec 09 17:22:01 <_tid> and it's awfull to patch the file is extracted after the makefile
Dec 09 17:22:02 <_tid> :)
Dec 09 17:23:18 <_tid> there is a way to alias gcc in the recipe so it overwrite this ?
Dec 09 17:26:20 <bluelightning> _tid: not really... we generally patch around stuff like this
Dec 09 17:26:41 <_tid> but patching the tarball is not easy :)
Dec 09 17:27:21 <bluelightning> _tid: right... but presumably you could do the extraction yourself and just patch out the makefile doing it?
Dec 09 17:27:40 <_tid> true.
Dec 09 17:27:45 <bluelightning> _tid: another option would be to break out js to a separate recipe; in fact we do have a recipe for spidermonkey js already
Dec 09 17:28:23 <_tid> hum
Dec 09 17:30:40 <bluelightning> although it's kind of an older version it seems
Dec 09 17:31:21 <_tid> well the one in pacparser is 1.7.0 also
Dec 09 17:32:56 <_tid> hum i like your idea i have to patch pacparser so it use the libjs in recipes-support
Dec 09 17:40:46 <_tid> still don't know how to do that :)
Dec 09 17:50:08 <mr_science> moin
Dec 09 17:51:52 <mr_science> _tid: maybe start by making pacparser depend on the libjs recipe
Dec 09 17:52:07 * mr_science missed the first part of the discussion
Dec 09 17:59:28 <_tid> yup :) it look for its libjs.a file... so i've to patch the Makefile not only the recipe... let's do that later, thanks a lot bluelightning and mr_science :)
Dec 09 18:34:21 <bmentink> anyone know why the "iw" command returns nl80211 not found? my wpa_supplicant has the driver support ..
Dec 09 18:49:05 <bmentink> anyone about?
Dec 09 18:57:07 <sgw_> bmentink: what's up?
Dec 09 18:58:38 <bmentink> sgw_: trying to find out why the "iw" tool is complaining about missing nl80211 driver
Dec 09 19:00:31 <sgw_> bmentink: looking quickly, iw tool are part of meta-openembedded, right?
Dec 09 19:06:44 <bmentink> sqw_: yes
Dec 09 19:15:15 <sgw_> bmentink: what kernel are you running and platform?
Dec 09 19:16:26 <bmentink> sqw_: running custom yocto layer based on dylan, 3.8.13 kernel
Dec 09 19:16:36 <sgw_> bmentink: do
Dec 09 19:17:48 <sgw_> bmentink: sorry are you sure that it has the nl80211 driver configured in?  I think that's a generic driver, maybe zeddii can weigh in, if you are using the linux-yocto kernel
Dec 09 19:18:31 <bmentink> sqw_: no, using linux-mainline kernel heavily patched by meta-beaglebone
Dec 09 19:19:48 <sgw_> bmentink: So can you confirm that the nl80211 driver is available on your booted machine?  I am not familiar with the iw since I mostly work with oe-core
Dec 09 19:20:06 <bmentink> from reading elsewhere looks like I might need nl80200 support in the actual wifi card driver
Dec 09 19:20:30 <sgw_> bmentink: you hit my limits, sorry.
Dec 09 19:20:31 <bmentink> sqw_: how do I see if nl80211 driver is available?
Dec 09 19:24:44 <fray> ls
Dec 09 19:24:47 <fray> opps
Dec 09 19:29:50 <otavio> mckoan|away: yes; this is due the missing branch from git SRC_URI. People are working in the patches to fix those in mailing list
Dec 09 19:31:32 <kergoth> i really hate bitbake's fetching stuff
Dec 09 19:54:34 <jackmitch|home> halstead: are there git issues ongoing at the moment?
Dec 09 19:54:52 <halstead> jackmitch|home, I'll check.
Dec 09 19:55:18 <jackmitch|home> halstead: git://git.yoctoproject.org/prelink-cross.git is the one failing
Dec 09 19:55:29 <halstead> jackmitch|home, Not that I see. I'll test that.
Dec 09 19:55:56 <jackmitch|home> halstead: hmm I take it back, seems a clone works, but not through oe
Dec 09 19:56:10 <jackmitch|home> will go investigate, sorry for wasting your time!
Dec 09 19:56:11 <halstead> jackmitch|home, Interesting.
Dec 09 19:56:23 <jackmitch|home> I think I read about someone else with this problem earlier
Dec 09 19:56:31 <jackmitch|home> something to do with the bitbake git fetcher changes
Dec 09 19:56:38 <halstead> jackmitch|home, No problem at all. Thanks for reporting early.
Dec 09 20:07:50 <_tid> i'd like to use cryptsetup and dm-crypt so i can have full disk encryption with yocto/poky but it need a initrd and the initramfs tools in yocto doesn't support arm. there is a solution ?
Dec 09 20:15:21 <rburton> _tid: what makes you think the initramfs support doesn't support arm?
Dec 09 20:15:24 <rburton> (that's news to me)
Dec 09 20:15:27 <rburton> hi sameo
Dec 09 20:15:45 <sameo> rburton: Hey Sir
Dec 09 20:16:22 <_tid> rburton : not initramfs but the tools provided within yocto
Dec 09 20:16:29 <rburton> _tid: what tools?
Dec 09 20:16:32 <_tid> :)
Dec 09 20:16:37 <rburton> (specifically)
Dec 09 20:16:49 <_tid> console-image-minimal-initramfs
Dec 09 20:17:19 <rburton> oh, because it says "efi"?
Dec 09 20:17:31 <_tid> well it doesn't want to build :)
Dec 09 20:17:38 <rburton> try deleting the "efi" bit?
Dec 09 20:17:41 <_tid> oki
Dec 09 20:18:18 <rburton> (if that is the issue, that needs to be made conditiional on architecture)
Dec 09 20:18:22 * rburton -> cooking
Dec 09 20:21:20 <_tid> ERROR: initramfs-live-install was skipped: incompatible with host arm-poky-linux-gnueabi (not in COMPATIBLE_HOST)
Dec 09 20:21:36 <_tid> well the tools use grub & so
Dec 09 20:22:00 <_tid> but i'm sure there is another way to build a initrd without those tools but i can't find any doc about that
Dec 09 20:24:53 <rburton> _tid: remove live-install too, that's an installer that you won't be using
Dec 09 20:25:13 <rburton> (this is an example image that lets you boot a live image, or install the image on the machine)
Dec 09 20:27:30 <_tid> hum nice
Dec 09 20:27:47 <_tid> that's a step further :)
Dec 09 20:28:43 <_tid> so i can try to add it in uboot and see what happen :)
Dec 09 20:28:58 <_tid> thx
Dec 09 20:29:47 <rburton> well, we don't have an image that does dm-crypt, but you can use that initramfs image as an example of how to build one.
Dec 09 20:29:54 <_tid> yop
Dec 09 22:45:28 <_tid> in a python extension the workdir (with setup.py) is src/pymod but i need to patch in the root dir, how can make my recipe aware of that ? :)
Dec 09 22:46:38 <_tid> if do S = ${WORKDIR}, the patching is ok but not the python setup and if i do S = ${WORKDIR}/src/pymod its the contrary
Dec 09 23:56:23 <bluelightning> _tid: you can set striplevel on the patch entry in SRC_URI to indicate how many directories to strip off when applying the patch
Dec 09 23:57:16 <_tid> bluelightning: it works for the path in the patchfile, not if i apply it beyond the root dir of src no ?
Dec 09 23:57:58 <_tid> i've workaound using do_compile_prepend and patch command...
Dec 09 23:58:44 <bluelightning> _tid: ok, I misunderstood; in that case you might need ;patchdir=../.. on the SRC_URI entry for the patch, or something like that
Dec 09 23:58:52 <_tid> oh cool
Dec 09 23:59:01 <_tid> thx
Dec 09 23:59:32 <_tid> the external libjs had solved my pb the recipe is working :)
Dec 10 00:00:03 <bluelightning> _tid: great :)
Dec 10 00:02:04 * bluelightning heads out
**** ENDING LOGGING AT Tue Dec 10 02:59:58 2013