**** BEGIN LOGGING AT Tue Jun 11 02:59:58 2013
Jun 11 05:37:20 <tasslehoff> any known issues around compiling an sdk for i686 on x86_64? a colleague had problems with the executables (like pkg-config) in the sdk I built. everything about the file looked sane, but it would just not run.
Jun 11 06:05:34 <tasslehoff> she gets: bash: ./arm-angstrom-linux-gnueabi-gcc: No such file or directory
Jun 11 06:05:59 <tasslehoff> though arm-angstrom-linux-gnueabi-gcc seems to be sane
Jun 11 06:12:18 <tasslehoff> must the sdk installer be ran on each developers machine? I ran it on my computer and added it to version control. other devs update the tree and have a symlink from /usr/local/oecore-i686 to the source tree
**** BEGIN LOGGING AT Tue Jun 11 06:41:24 2013
Jun 11 07:19:54 <mckoan> good morning
Jun 11 08:21:46 <bluelightning> morning all
Jun 11 08:23:44 <tasslehoff> morning.
Jun 11 08:24:24 <tasslehoff> if I compile an i686-sdk on two different machine (32 and 62 bit), should they be identical if built from the same git revisions?
Jun 11 08:28:47 <mckoan> tasslehoff: AFAIK yes
Jun 11 08:30:25 <bluelightning> tasslehoff: when you say i686 SDK you mean SDKMACHINE has been set?
Jun 11 08:30:30 <bluelightning> to i686 that is
Jun 11 08:31:45 <tasslehoff> bluelightning: yes.
Jun 11 08:32:47 <bluelightning> tasslehoff: in that case they should be the same
Jun 11 08:32:54 <tasslehoff> are there any open issues with crosscompilation or relocation of SDKs?
Jun 11 08:32:59 <tasslehoff> or known limitations
Jun 11 08:36:09 <bluelightning> tasslehoff: not that I'm aware of, but it's not something I'm particularly close to
Jun 11 08:46:00 <bluelightning> tasslehoff: if you're experiencing a problem it may be worth emailing the mailing list and CCing Laurentiu Palcu
Jun 11 08:46:59 <tasslehoff> bluelightning: ok. found something now. the gcc compiled on my 64 bit system runs fine on another 32 bit system with my user. on another 32 bit system as another user, it does not.
Jun 11 08:48:07 <bluelightning> tasslehoff: can you be more specific about the problem on the other system?
Jun 11 08:49:19 <silvio_l_> morning all
Jun 11 08:49:58 <tasslehoff> wrote it earlier, but perhaps you were not here then: bash: ./arm-angstrom-linux-gnueabi-gcc: No such file or directory
Jun 11 08:56:17 <bluelightning> tasslehoff: is the sdk in the exact same path on the other users machine as it was installed to on yours?
Jun 11 08:59:39 <tasslehoff> bluelightning: found the cause http://hastebin.com/duyonotive.coffee
Jun 11 09:00:00 <tasslehoff> eh. complete paste follows.
Jun 11 09:01:07 <tasslehoff> bluelightning: http://hastebin.com/gocawabiwa.coffee
Jun 11 09:02:02 <tasslehoff> the link to ld-linux.so.2 is what breaks it. 
Jun 11 09:03:03 <bluelightning> tasslehoff: I think Laurentiu would be the best person to talk to about this
Jun 11 09:03:14 <bluelightning> since he wrote the relocation code
Jun 11 09:04:11 <tasslehoff> bluelightning: ok. I'll post on the ML
Jun 11 09:19:32 <SorenHolm> Hi
Jun 11 09:20:07 <SorenHolm> I'm getting hit by a QA-error when building base-files. "Fixup Perms: Unable to correct directory link". Can you confirm that?
Jun 11 09:49:13 <silviof1> -morning all
Jun 11 10:05:21 <ndec> hi. does anybody know if meta-qt5 works (or not) with oe-core/dylan ?
Jun 11 10:14:58 <SorenHolm> Can anybody confirm that base-files suffers from te QA-issue : " Unable to correct directory link, target already exists: /var/log -> /var/volatile/log" ?
Jun 11 10:17:09 <jackmitchell> ndec: I believe people are working on it, but it's not production ready
Jun 11 10:17:49 <ndec> jackmitchell: yes, i know that it's not ready, but i wanted to check if it's 'workable' with dylan, or only with master branch?
Jun 11 10:18:24 <jackmitchell> ndec: if it doesn't have a 'dylan' branch, then I would assume master
Jun 11 10:29:37 <tasslehoff> I suspeect maybe JaMa knows the answer to ^
Jun 11 10:35:54 <JaMa> ndec: yes it works
Jun 11 10:36:50 <JaMa> it has dylan and master branches, both now work with dylan (but master can became incompatible later)
Jun 11 11:10:17 <ndec> JaMa: ok, thanks. i am actually going to need dylan + meta-qt5, so thanks for maintaing it!
Jun 11 11:10:35 <ndec> JaMa: btw, what tests are you doing with Qt5? which images are you building?
Jun 11 11:10:56 <ndec> and are you building any more 'embedded' images too? 
Jun 11 11:11:30 <ndec> i mean, no X11, no wayland backend, but with directfb, minimal and/or eglfs.
Jun 11 11:11:57 <JaMa> we're using wayland, so I'm testing only wayland backend
Jun 11 11:12:17 <JaMa> ericben did some tests with directfb IIRC
Jun 11 11:13:14 <ndec> are all backend built by default? (i haven't started any build for now)
Jun 11 11:15:17 <JaMa> no, e.g. you need to select gl implementation
Jun 11 11:16:28 <ndec> ok, i will check into that. and ask you if needed ... 
Jun 11 11:16:51 <ndec> ericben: see ^^. do you have branch with a 'working' directfb build?
Jun 11 11:19:32 <JaMa> I think he was testing it with master branch :)
Jun 11 11:19:41 <JaMa> see his commits
Jun 11 13:02:17 <tasslehoff> bluelightning: is Laurentiu on irc? 
Jun 11 13:19:50 <SorenHolm> Can anyone here compile xf86-video-intel. It fails for me needing dri2.h
Jun 11 15:28:56 <pb_> morning all
Jun 11 16:17:35 <fischerm> I just updated from somewhere around 94e3f182 to master for oe-core and now I get http://pastebin.com/CsaEvYF0, any ideas?
Jun 11 16:19:50 <Crofton|work> unknown pasteid ...
Jun 11 16:20:17 <fischerm> Crofton|work: http://pastebin.com/raw.php?i=CsaEvYF0
Jun 11 16:21:23 <fischerm> Crofton|work: does this one work?
Jun 11 16:21:30 <Crofton|work> yes
Jun 11 17:18:51 <fischerm> seems like commit 4ec66dc5f38913056942e1288c0b01a00ea0551f -     packagegroup-base-vfat: include dosfsprogs
Jun 11 17:18:54 <Crofton|work> kergoth, ^^^ seems to come from http://git.openembedded.org/openembedded-core/commit/?id=4ec66dc5f38913056942e1288c0b01a00ea0551f
Jun 11 17:18:55 <fischerm> broke it for me
Jun 11 17:19:28 <Crofton|work> fischerm, grep your oe-core directory for dosfsprogs
Jun 11 17:19:47 <fischerm> Crofton|work: nope
Jun 11 17:19:52 <fischerm> Crofton|work: nada
Jun 11 17:19:56 <Crofton|work> weird
Jun 11 17:20:17 <Crofton|work> normally RP and kergoth are flawless
Jun 11 17:20:21 <fischerm> Crofton|work: someone would have noticed if it would be missing in tree I assume
Jun 11 17:23:23 <bluelightning> kergoth just sent a patch to fix it
Jun 11 17:23:25 <bluelightning> btw
Jun 11 17:24:06 <Crofton|work> bluelightning, thanks!
Jun 11 17:24:22 <kergoth> yeah, sorry about that, I think I accidentally mixed up my patch series and sent one without the fix
Jun 11 17:24:40 <kergoth> that'll teach me to submit patches on Monday
Jun 11 17:24:41 <Crofton|work> yeah, i figured that is what happend
Jun 11 17:24:49 <Crofton|work> fischerm, get some rest :)
Jun 11 17:25:05 <fischerm> :)
Jun 11 17:25:21 <Crofton|work> well, if you are not goin gto rest look at the oe-core list archives for the fix :)
Jun 11 17:25:54 <fischerm> Crofton|work: That's what I'm doing
Jun 11 17:26:44 <fischerm> Crofton|work: oh ... the patch is what I actually manually applied to make it work again :)
Jun 11 17:26:49 <Crofton|work> Be sure to ask kergoth why he didn't write bitbake in haskell
Jun 11 17:27:00 <fischerm> kergoth: Why didn't you write bitbake in haskell
Jun 11 17:27:42 <bluelightning> because he doesn't like pain?
Jun 11 17:27:43 <bluelightning> ;)
Jun 11 17:29:04 <fischerm> bluelightning: such a beautiful language
Jun 11 17:29:21 <bluelightning> I haven't honestly used it since my university days
Jun 11 17:29:29 <bluelightning> but it made my head hurt back then...
Jun 11 17:31:18 <fischerm> bluelightning: yeah... it's like the opposite of java. Every line written in haskell actually does something
Jun 11 17:32:29 <kergoth> I didn't know haskell, but then, I didn't know python either, so that's not much of an argument ;)
Jun 11 17:33:00 <fischerm> kergoth: so close ... damn :D
Jun 11 17:33:25 <kergoth> python was just an easy route to go, and we did use some of gentoo's portage code at first, though not much
Jun 11 17:33:53 <fischerm> I see
Jun 11 17:34:01 <fischerm> I got another error :-/
Jun 11 17:34:09 <kergoth> what error?
Jun 11 17:34:47 <fischerm> http://pastebin.com/r5gysimv
Jun 11 17:34:49 <fischerm> gettext this time
Jun 11 17:40:30 <fischerm> kergoth: any idea?
Jun 11 17:48:41 <kergoth> not a clue on that one
Jun 11 17:49:04 <fischerm> kergoth: would checking out the 'dylan' branch bring me back to a usable state?
Jun 11 17:49:42 <Crofton|work> JaMa, I am 99% certain the swig pathc had the -M
Jun 11 17:49:46 <kergoth> impossible to say without knowing the cause
Jun 11 17:49:54 <kergoth> i didn't touch ettext, so it's not something from one of my patchsets
Jun 11 17:49:57 <kergoth> its something else entirely
Jun 11 17:50:20 <fischerm> ok
Jun 11 17:50:25 <Crofton|work> llooks like a missing lcurses?
Jun 11 17:50:44 <fischerm> Crofton|work: yeah
Jun 11 17:51:18 <JaMa> Crofton|work: that wasn't me complainig about it :)
Jun 11 17:51:26 <Crofton|work> hmm
Jun 11 17:51:41 <Crofton|work> doh
Jun 11 17:51:45 <Crofton|work> sorry that was khem
Jun 11 17:51:52 <JaMa> Crofton|work: I guessed it was and wasn't detected as it's short file and git sometimes don't detect renames in them well
Jun 11 17:51:59 <Crofton|work> I cut and paste the git send-email line from the README
Jun 11 17:52:15 <JaMa> that's right thing to do :)
Jun 11 17:52:26 <Crofton|work> heh
Jun 11 17:52:36 <JaMa> Crofton|work: as you've already pinged me :) any update about gnuradio failing?
Jun 11 17:52:41 <JaMa> with docs..
Jun 11 17:52:47 <Crofton|work> gah
Jun 11 17:52:53 <Crofton|work> I need to look at that
Jun 11 17:52:59 <Crofton|work> didn't get to it last week
Jun 11 17:53:08 <Crofton|work> ended up fighting with ice
Jun 11 17:53:22 <Crofton|work> we did look and I think I know how to patch it for now
Jun 11 17:53:30 <Crofton|work> Just need some time to do it
Jun 11 17:53:47 <JaMa> ok
Jun 11 19:58:08 <SorenHolm> JaMa: Thanks for the email. How do I set the PACKAGECONFIG. I have tried adding opengl to DISTRO_GLFEATUES (angstrom) and rebuilding xserver-xorg. It should be enough right?
Jun 11 20:09:48 <JaMa> SorenHolm: check with bitbake -e xserver-xorg
Jun 11 20:09:57 <JaMa> to see if all configure options are set correctly
Jun 11 20:15:58 <SorenHolm> JaMa: Will do. What does the weird []-syntax do anyway ?
Jun 11 20:20:41 <JaMa> it's called varflags
Jun 11 21:14:38 <SorenHolm> JaMa: ok, thanks.
Jun 11 22:22:41 <SorenHolm> JaMa: is there a better way to append to DISTRO_FEATURES than putting DISTRO_FEATURES_append = " opengl" in local.conf ?
Jun 11 22:29:59 <kergoth> not really, no
Jun 11 22:32:03 <JaMa> SorenHolm: some distros have DISTRO_FEATURES divided into smaller variables, in that case you can append to one of those, but that's all you can expect
Jun 11 22:35:50 <kergoth> at mentor, we inherit http://git.yoctoproject.org/cgit/cgit.cgi/meta-mentor/tree/classes/user_features.bbclass to make it easier to both add to and remove from DISTRO_FEATURES from local.conf
Jun 11 22:35:57 <kergoth> can be handy
Jun 11 22:45:06 <dbfi> Any idea why there is "ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored." during do_rootfs when using recent master-branch?
Jun 11 23:11:56 <mr_science> i just updated but haven't seen that one
Jun 11 23:12:26 <mr_science> things can get a little wonky if you update and don't rm -rf tmp and rebuild
Jun 11 23:12:44 <mr_science> are you doing a clean build after updating?
Jun 11 23:18:29 <dbfi> Yes, a clean build after update
Jun 11 23:22:14 <dbfi> It appears in the log after update-alternatives: for boot/uImage
Jun 11 23:23:11 <mr_science> other than repeating the error message, i got nothin'
Jun 11 23:23:49 <mr_science> *something* must've fubar'd preload for libpseudo but i have no idea what...
**** ENDING LOGGING AT Wed Jun 12 02:59:58 2013