**** BEGIN LOGGING AT Tue Feb 09 02:59:59 2016 Feb 09 09:21:50 mornin Feb 09 09:25:16 good morning Feb 09 14:15:06 JaMa: ping Feb 09 14:19:49 pong Feb 09 14:32:59 hello Feb 09 14:33:57 JaMa: do you suggest to use INSANE_SKIP_XXX += or just = ? Feb 09 14:34:31 some recipes do add items, other just set the variable Feb 09 14:35:10 is it maybe expected to be set in local.conf or in distro ? Feb 09 14:43:35 no strong opinion but I would probably use += Feb 09 14:44:20 there are discording examples in oe-core Feb 09 14:45:02 ok then, no need to resend the patch for klibc Feb 09 15:03:56 rburton, was someone at Intel fighting with building atlas? Feb 09 15:11:35 Crofton|work: not as far as i can recall, but i wouldn't be entirely surprised if someone was Feb 09 15:11:51 Crofton|work: are you hoping for a preexisting recipe? Feb 09 15:11:57 yeah :) Feb 09 15:12:05 I suspect they tried and got angry like me Feb 09 15:12:14 I'd been talking to Paul about it a while back Feb 09 15:12:55 I ran into someone at fosdem who needs lapack for something Feb 09 15:13:03 somethign cool enough to interest me :) Feb 09 15:31:30 atlas is nightmare Feb 09 15:31:57 'lets build with whatever set of flags we can invent. and do it few times. just in case' Feb 09 15:35:42 hrw: extra fun when it ends in an infinite compile loop Feb 09 16:03:32 niiiice Feb 09 16:03:36 and i thought numpy was bad Feb 09 16:03:52 jhah Feb 09 16:08:03 suihkulokki: usually it just takes huge amount of time Feb 09 16:08:16 and forget that you will get new architecture merged Feb 09 22:08:21 I am trying to get PyGreSQL to stop looking at the build host for information. In the bitbake rule is there a way to get the version of postgresql that was built, Or is there a better way of getting the information setuptools needs for PyGreSQL? **** ENDING LOGGING AT Wed Feb 10 02:59:59 2016