**** BEGIN LOGGING AT Wed Jan 27 02:59:59 2016 Jan 27 13:44:40 brb, ngita sako'g makaon diring lugara. Jan 27 14:04:13 florian, will you be at FOSDEM? Jan 27 14:06:16 Crofton: unless anythign evil hapens i will be there Jan 27 14:07:33 Great Jan 27 14:07:43 you ave the table cloth and did you find stickers? Jan 27 14:07:51 I'm in Berlin this week Jan 27 14:08:26 belen shoudl have a toaster showing rough build data for my demo systems Jan 27 14:09:11 I'm trying to build pyephem with tools on a device Jan 27 14:09:23 but this message has me scratching my head Jan 27 14:09:25 http://pastebin.com/H0NsAU3N Jan 27 14:10:44 Crofton|work should know ;) Jan 27 14:10:55 hah Jan 27 14:11:07 Crofton: yes we have quite some stickers left and soem flyers. Jan 27 14:11:20 florian, the keeper of sacred OE stand kit? Jan 27 14:11:31 sort of :) Jan 27 15:42:20 hmm, I run setup.py install for something that compiles an extension, but the compiler refers to build macine sysroot Jan 27 15:42:29 oh python gurus, what it the matter Jan 27 16:37:30 a python task in a recipe is always executed by the same interpretter as used to invoke bitbake (i guess?). Is it possible to make a task execute in the context of python-native? essentially i want to access python-modules that have been installed to my native sysroot (but not necessarily available in the host sysroot) from my task Jan 27 16:40:28 the closest thing i've managed to do is to inherit pythonnative.bbclass and then from my task shell ${PYTHON} myscript.py (which then is a meta-file of my recipe). But it would be much cleaner if i could put the contents of myscript.py directly into my recipe and flag it as a python-native task Jan 27 16:41:06 at the same time i understand that bitbake cannot be aware of package-specifics such as python-native (part of oe-core), but still, i was hoping there's some other mechanism in OE that allows me to do this in a less hacky way Jan 27 16:41:32 not really, no. we can't define an arbitrary interpreter for a task at this time Jan 27 16:42:43 if you really want to run the python-native then invoking it directly is the best way really Jan 27 16:44:00 ok, thanks Jan 27 17:11:20 I have a image.bb without PR defined and everything is fine. If I put PR = "r1" I receive an error: install: cannot stat 'pathfirfile: No such file or directory It's a file that is on image.bb recipe that I make a manual install Jan 27 17:11:58 I need to add a directory for that PR version? Jan 27 17:14:55 you really haven't given us enough information to tell you the problem Jan 27 17:15:16 * paulg_ notes the git uprev broke the build with unpkgd files... Jan 27 17:16:00 kergoth: sorry that is for me? Jan 27 17:44:28 when I modify the PR of a recipe I need to change the name of the folder where SCR_URI files are? Jan 27 18:13:50 no Jan 27 18:14:13 should be just "files" or versioned Jan 27 18:14:17 only if PR is in that folder, whichi t should not be Jan 27 18:14:33 PR is not part of the version Jan 27 18:16:17 well, PR is local and PV is upstream Jan 27 18:17:48 PR is mainly so you can upgrade the packages you build Jan 27 18:19:35 also nowadays you don't need to modify PR at all, just use a PR server Jan 27 18:21:35 it's a hack to add some files on image Jan 27 18:35:58 oe have any mailing list for newbies? just to track and try learn more? Jan 27 19:01:57 nine_pt: no but feel free to subscribe and lurk on openembedded-devel@lists.openembedded.org . Also as long as you don't continually spam the list without searching and trying something first you should just ask away. Jan 27 19:04:31 vmeson: thanks **** ENDING LOGGING AT Thu Jan 28 02:59:58 2016