**** BEGIN LOGGING AT Tue Feb 28 03:00:01 2017
Feb 28 12:20:11 <jackmitch_work> how does one use python from the recipe sysroot, I have to call out to a natively built python module but it says it can't be found
Feb 28 12:20:25 <jackmitch_work> however, when I look in the recipe-sysroot-native, the module is there
Feb 28 12:20:39 <rburton> what from?
Feb 28 12:20:40 <jackmitch_work> the python that I call has # /usr/bin/env python at the start of the script
Feb 28 12:20:55 <rburton> inherit pythonnative in your recipe
Feb 28 12:20:58 <jackmitch_work> will this call out to the host python, or does it get magically fixed
Feb 28 12:21:04 <rburton> yes, that will call the host python by default
Feb 28 12:21:11 <jackmitch_work> I did that and it didn't make any difference
Feb 28 12:21:11 <rburton> native python is opt-in
Feb 28 12:22:27 <jackmitch_work> so I have this so far, http://ix.io/nPN
Feb 28 12:23:16 <jackmitch_work> maybe as it's calling "env python" it's looking for python2 and bypassing the python3native?
Feb 28 12:23:25 <rburton> well yes
Feb 28 12:23:30 <rburton> if you use env python, you get python2
Feb 28 12:23:41 <jackmitch_work> not in my host distro ;)
Feb 28 12:23:45 <rburton> your host distro is wrong
Feb 28 12:23:51 <rburton> literally everyone else does something else
Feb 28 12:23:53 <rburton> *literally*
Feb 28 12:24:05 <jackmitch_work> isn't env python just the hosts default python?
Feb 28 12:24:09 <rburton> no
Feb 28 12:24:16 <rburton> well, env python is "search for python"
Feb 28 12:24:24 <rburton> everyone in the world apart from arch says that is py2
Feb 28 12:24:28 <rburton> including us
Feb 28 12:24:40 <rburton> and if you want the native py3 we built, that is called python3
Feb 28 12:25:11 <jackmitch_work> ok, so to use the python3 in the native sysroot I need to patch the native python module to call env python3, and then all should work
Feb 28 12:25:46 <rburton> yes
Feb 28 12:26:08 <jackmitch_work> or I could call the python module directly using python3 maybe
Feb 28 12:26:19 <jackmitch_work> ok; i've got enough to work on - the default python thing stumped me
Feb 28 12:26:23 <rburton> not from bitbake land as that's running in host python3
Feb 28 12:26:42 <rburton> lesson is that arch did a bad thing and is too stubborn to admit it :)
Feb 28 14:40:46 <Crofton|work> fray, there is a patch on the list reverting something done by Jackie @wr to fuse
Feb 28 19:07:23 <Crofton|work> so building fftw no longer creates the fftw package
Feb 28 19:07:29 <Crofton|work> just fftwf etc
Feb 28 19:07:50 <Crofton|work> so if you try to install fftw via CORE_IMAGE_EXTRA_INSTALL the image will not build
Feb 28 19:07:55 <Crofton|work> anyone have a work around
Feb 28 21:04:49 <khem> Crofton|work: I think its good to not geenrate empty package 
Feb 28 21:04:56 <khem> use the version you want 
Feb 28 21:05:10 <khem> in CORE_IMAGE_EXTRA_INSTALL
Feb 28 21:12:49 <Crofton|work> but CORE_IMAGE_EXTRA.. leads to ERROR: Nothing RPROVIDES 'fftwf' (but /home/balister/src/oe-core/oe-core/../meta-sdr/recipes-images/images/uhd-dev-image.bb RDEPENDS on or otherwise requires it)
Feb 28 21:16:29 <khem> hmmm
Feb 28 21:16:40 <khem> so there is no ipks at all ?
Feb 28 21:18:12 <Crofton|work> ipks are thre
Feb 28 21:18:54 <Crofton|work> [balister@thuvia build]$ ls buildhistory/packages/armv7ahf-neon-oe-linux-gnueabi/fftw
Feb 28 21:18:54 <Crofton|work> fftw      fftw-doc      fftwl-wisdom    fftw-wisdom-to-conf  libfftwf
Feb 28 21:18:54 <Crofton|work> fftw-dbg  fftwf-wisdom  fftw-staticdev  latest               libfftwl
Feb 28 21:18:54 <Crofton|work> fftw-dev  fftw-locale   fftw-wisdom     libfftw
Feb 28 21:19:10 <Crofton|work> fftw is because I set allowempty and messed with RPROVIDES
Feb 28 21:19:34 <Crofton|work> trying to create an image with fftwf so people can build a a package that needs it, but othing else does
Feb 28 22:05:45 <khem> so its actually libfftw
Feb 28 22:05:57 <khem> it means its doing debian renaming 
Feb 28 22:06:26 <khem> so should work if you disable debian renaming 
Feb 28 22:25:01 <Crofton|work> ok, will try turning off debian renaming
Feb 28 22:27:43 <bluelightning> erm
Feb 28 22:28:10 <bluelightning> debian renaming doesn't apply to what's specified in IMAGE_INSTALL or variables like CORE_IMAGE_EXTRA_INSTALL that feed into it
Feb 28 22:28:18 <bluelightning> Crofton|work: khem: ^
Feb 28 22:28:27 <bluelightning> those deal with the pre-renamed names
Feb 28 22:28:58 <bluelightning> pretty much everything in recipe space does
Feb 28 22:31:59 <Crofton|work> you see the entire convo?
Feb 28 22:32:22 <Crofton|work> we changed fftw to build fftwf and fftwl
**** ENDING LOGGING AT Wed Mar 01 03:00:02 2017