[04:58] <micahg> looks like upstream Chromium almost fixed the build on arm :)
[05:07] <suihkulokki> micahg: I and markos attached patches that fix chromium on armel/armhf to the debian bug
[05:08] <micahg> suihkulokki: now I find out, I just uploaded a new version :)
[05:08] <micahg> ok, I"ll grab them for the next updat
[06:03] <micahg> suihkulokki: I realized that I was only checking for armel in debian/rules, I fixed that for the next upload
[10:28] <ogra_> hey kalikiana, good to see you around :)
[10:31] <kalikiana> heyhey
[10:32] <kalikiana> I checked out #arm before, seems the cool kids are all here :-P
[10:32] <ogra_> well, here is where the community is ... way more important than the other channel ;)
[10:56] <ogra_> hey micahg, whats that patch you talked about last night ? i think kalikiana would like to know about it
[10:56] <micahg> ogra_: patch, what patch?
[10:56] <ogra_> chromium
[10:56] <kalikiana> micahg: oh, you're there, was just typing a mail
[10:57] <micahg> I think it might work now without any patches
[10:57] <micahg> I'm waiting on the first armel build from yesterday
[10:57] <kalikiana> micahg: so who builds it? where's the package source?
[10:57]  * ogra_ only saw that riku said he attached the patches to a bug ... but didnt mention the bug number
[10:58] <ogra_> kalikiana, in the ubuntu archive i guess
[10:58] <ogra_> (precise sources)
[10:58] <kalikiana> I couldn't find working steps to get a cross-compile setup with all packages
[10:58] <micahg> kalikiana: chromium-browser? the same way anything else in the archive is built
[10:58] <kalikiana> micahg: well, but a human must have tested it :-)
[10:59] <micahg> kalikiana: I think Debian must have upstream their patches
[10:59] <kalikiana> meh, so yet another possible team to poke...
[10:59] <ogra_> why ?
[10:59] <ogra_> they will just end up in precise
[10:59] <micahg> I also found a bug in the packaging, which I'll fix for the next upload to get armhf
[10:59] <ogra_> just pull the precise source package for your project
[10:59] <micahg> we don't merge from Debian for Chromium
[11:00] <ogra_> micahg, that would be helpful, given we will make the switch today :)
[11:00] <kalikiana> micahg: so do you have a working build setup?
[11:00] <kalikiana> I'm running into broken deps
[11:00] <ogra_> (armel will become unsupported from today on)
[11:00] <micahg> kalikiana: no, these are archive builds, I upload 2 recent stable releases to precise
[11:01] <kalikiana> hmm
[11:01] <kalikiana> I really need to build it locally
[11:01] <micahg> ogra_: I figured another chromium upload will come in a week or 2, if you need it sooner and armel works, I can upload with the armhf fix
[11:01] <ogra_> yes please, we will stop caring for armel from today on
[11:02] <ogra_> we wont stop building it, but nobody will look at issues
[11:02] <micahg> ok, I'll keep an eye on it
[11:02] <kalikiana> micahg: can you recommend a person who cross-compiles usually?
[11:02] <micahg> kalikiana: only one I know is suihkulokki :)
[11:02] <infinity> ogra_: "nobody" is a bit much, I always watch build issues on all ports.
[11:02] <infinity> ogra_: I just prioritize. :P
[11:02] <ogra_> infinity, hey, you are not supposed to be up at that time !
[11:03]  * micahg does that too :)
[11:03] <infinity> ogra_: I'm not, it's all in your head.
[11:03]  * micahg is also not supposed to be up now
[11:03] <kalikiana> micahg: k, I'll wait for him then
[11:03]  * ogra_ was just trying to secretly spread FUD while infinity wasnt watching ...
[11:03] <ogra_> damned !
[11:03] <kalikiana> (or her)
[11:04] <infinity> I'll be sure to call Riku a her the next time I see him. ;)
[11:04] <micahg> kalikiana: did you try the instructions on the linaro wiki?
[11:04] <ogra_> lol
[11:04] <kalikiana> micahg: yes. but gconf2 and bzip2 at least are broken
[11:05] <micahg> file bugs?
[11:06]  * infinity wonders why everyone gets so excited about cross-compiling.
[11:06] <infinity> Especially to the point of wasting days/weeks trying to make it all work right.
[11:07] <kalikiana> infinity: because it is several times faster
[11:07] <infinity> When you could just build natively (sure, more slowly), but be done with it.
[11:07] <infinity> kalikiana: Not when you factor in all the annoyance. :P
[11:08] <kalikiana> well, the setup is actually simple. the problem is really that arm is relatively recent
[11:08] <ogra_> yeah, its such a waste
[11:08] <infinity> "recent"?
[11:08] <ogra_> heh
[11:08] <suihkulokki> we even wronte instructions to cross-compile chromium: https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/ChromiumCrossCompile
[11:08] <kalikiana> infinity: as in packaging :-)
[11:08] <kalikiana> yes
[11:08] <kalikiana> and those don't do it
[11:08] <ogra_> we have it since jaunty ...
[11:08] <kalikiana> hey suihkulokki
[11:08] <ogra_> and debian has it since ... hmm, forever
[11:09] <kalikiana> suihkulokki: gconf2 and bzip2 are broken
[11:09] <suihkulokki> bug# ?
[11:09] <kalikiana> suihkulokki: the packages don't install
[11:09] <ogra_> infinity, do you know if anyone talked to kate about armhf ? we should make her announce it in the FF announcement i think
[11:10] <kalikiana> suihkulokki: is it expected to work as described there, as in used by somebody on a regular basis?
[11:10] <infinity> ogra_: I brought it up when I spoke to her on the phone on Monday, but we didn't discuss a formal announcement.
[11:10] <suihkulokki> kalikiana: yes if you don't deviate from the steps
[11:10] <ogra_> ok, i'll ping here if she is up to make sure she doesnt forget
[11:11] <infinity> ogra_: Also, I think we need to be careful how we word such an announcement.
[11:11] <infinity> ogra_: People seem gung-ho to say things like "we only support armhf now!" which is patently untrue.
[11:11] <infinity> ogra_: It's just that we've selected armhf as the LTS arch.
[11:11] <ogra_> k
[11:12] <ogra_> lets make sure that goes into the announcement then
[11:12] <kalikiana> suihkulokki: I don't. so is there somebody who I could poke about those packages? I'd think bugs might not exactly receive attantion very quickly
[11:12] <ogra_> though i suspect we will stop building armel images for some flavours
[11:12] <ogra_> at least until your LP changes are ready
[11:12] <infinity> ogra_: (From a Canonical standpoint, yes, we only support armhf now, but Canonical != Ubuntu, and we need to be clear about that, or just steer clear of such statements, I prefer the latter)
[11:12] <suihkulokki> kalikiana: pastebin your errors please (as well as what is in your sources.list)
[11:12] <infinity> ogra_: I intend to drop armel images for !omap tomorrow.
[11:13] <infinity> ogra_: But installer/image support != archive support.  Again, distinction is key. :)
[11:13] <ogra_> if we can it would be nice to keep el and hf for ac100
[11:13] <ogra_> simply for the binary driver
[11:13] <infinity> ogra_: Yeah, that's fair.  It's also a good platform for us to keep testing armel on as a community port.
[11:13] <infinity> ogra_: Alright, I'll keep omap and ac100, and drop mx5 and omap4.
[11:14] <ogra_> ++
[11:14] <infinity> (The reason I'm keeping omap is simply because it's the only kernel that builds from mainline, so it's "free" from a maintenance perspective)
[11:14] <ogra_> yeaqh
[11:15] <infinity> Plus, we might free up some beagles from the DC soon, and pass them around to people, thus making omap useful. ;)
[11:17] <infinity> ogra_: Oh, we did get some indication at Connect that nvidia is actually planning armhf builds of their binary driver.
[11:17] <infinity> ogra_: I was told they've already done builds in-house, they're just working on the tarball drop.
[11:17] <ogra_> yeah, but they dont exist yet and we have no promises they will be there by release
[11:17] <infinity> So, we'll see.
[11:18] <ogra_> i'm carefule about them if it comes to timelines (unlike ndec whom i belive blindly if he says it will come)
[11:18] <infinity> Heh.
[11:18] <infinity> Well, this was engineers, not legal.
[11:18] <kalikiana> suihkulokki: http://pastebin.ubuntu.com/844219/
[11:18] <infinity> Which is a double-edged sword, I guess.
[11:19] <infinity> The engineers are doing the real work, and they know what they've done.
[11:19] <infinity> Then again, they don't get to do the final release to the website.
[11:19] <ogra_> yep
[11:19] <ogra_> fi engeneering had a say, we would have everything in since a year or two, i know
[11:21]  * micahg still would like an mx51 kernel for precise, but fears that's not happening
[11:22] <infinity> micahg: For babbage, or efika?
[11:22] <ogra_> micahg, complain to linaro, we donmt maintain that arch :)
[11:22] <micahg> efika
[11:22] <infinity> micahg: For efika, talk to markos.
[11:22] <infinity> micahg: He promised me a kernel.
[11:22] <ogra_> for what ? netbook or nettop ?
[11:22] <infinity> micahg: I even promised him unofficial image enablement if he got me a working kernel. :P
[11:22] <infinity> ogra_: Yes.
[11:22] <ogra_> there was an or in the question
[11:23] <infinity> ogra_: (He seemed to think he could build one that would work on both)
[11:23] <micahg> ogra_: I have both, would prefer the smartbook
[11:23] <ogra_> unless they very recently started having a unified kernel
[11:23]  * ogra_ too, i have one here as well
[11:23] <micahg> although, I guess I'd prefer an armhf kernel for mx51 :)
[11:23]  * infinity has a smarttop.
[11:23] <infinity> micahg: Kernels are FP agnostic.
[11:23] <micahg> oh, ok, cool
[11:24] <ogra_> packages arent indeed :)
[11:24] <infinity> micahg: But seriously, nag markos.  If he can get me something that's sane, I'll get it into universe.
[11:24] <micahg> infinity: I'm happy to be the second reviewer on that ;)
[11:24] <infinity> micahg: I wouldn't mind a vaguely current kernel on my efika either. :P
[11:25] <suihkulokki> kalikiana: argh. looks like I have uploaded a precise targetted gconf to the ppa's oneiric side
[11:25] <infinity> (Though it is the slowest ARM device in my house)
[11:25] <ogra_> you dont have beacgle A/B versions ?
[11:25] <suihkulokki> kalikiana: tho the bzip2 should install just fine
[11:25]  * ogra_ has a beagle A1, thats definitely the slowest
[11:26] <micahg> suihkulokki: is there something we should fix in precise for cross compiling?
[11:26] <infinity> ogra_: I have no beagles.
[11:26] <ogra_> ah
[11:26] <infinity> ogra_: My N900 used to be the slowest ARM device on my desk, but I sold it to Sledge.
[11:26] <ogra_> yeah, and thats already twice as fast as an A1
[11:27] <infinity> ogra_: So, now I have the efikaMX, an i.MX53, a Panda, an ac100, and an LGP999 (Tegra2 phone).
[11:27] <kalikiana> suihkulokki: ah. yes, sorry, bzip seems okay at this point. I tried a different ppa before, but made sure to clean up before I pasted
[11:27] <ogra_> and has enormous amounts of ram compared...
[11:27] <infinity> It's a bit sad that the phone is actually the fastest of the bunch.
[11:27] <kalikiana> suihkulokki: any chance you could re-upload it correctly? anything I can bribe you with? :-P
[11:27] <ogra_> stop using it as a phone then and send it to lamont as a buildd :)
[11:28] <infinity> I used it as a buildd during the armhf bootstrap. :P
[11:28] <ogra_> heh
[11:28] <ogra_> we should make tobin build a cluster of them in a rack case :)
[11:31] <suihkulokki> kalikiana: testing.. will ping back in a hour or so
[11:32] <suihkulokki> micahg: gconf2 is probably the most annoying thing missing multiarch conversion in precise.
[11:33] <infinity> micahg: So, I harassed markos, and he said they're (A) working on 3.2 for efika/mx51, and (B) it will be a unified smarttop/smartbook kernel.
[11:33] <infinity> micahg: And he's going to try to get me half-functional bits ASAP so I can work with them in my copious free time.
[11:33] <micahg> suihkulokki: we might be able to do something about that, it's still got a lot of reverse dependencies though
[11:34] <micahg> infinity: that's awesome, let me know if I can help with my copious amounts of free time
[11:34] <suihkulokki> can't we just make chromium not use gconf? =)
[11:35] <micahg> not for another year :)
[11:35]  * micahg wonders if they have an option to s/gconf/gsettings/
[11:37] <kalikiana> suihkulokki: wrt bzip2, I get this http://pastebin.ubuntu.com/844238/
[11:39] <kalikiana> removing gconf from chromium shouldn't be that hard, but more time probably than fixing gconf2 packages :-P
[11:39]  * micahg has plenty of other archive cleanup work to do
[11:39] <ogra_> well, it eventually needs to move to gsettings anyway
[11:39] <infinity> kalikiana / suihkulokki: That looks like the bzip2 in the linaro PPA was built with a broken gzip.  We've fixed that bug in precise... Though, if this is an oneiric PPA, it's a crap shoot if it'll break or not. :/
[11:40] <kalikiana> yes, it's oneriric I need to build for
[11:40] <infinity> kalikiana: You can work around it by just doing "dpkg --force-overwrite -i /var/cache/apt/archives/libbz2-1.0_1.0.5-6ubuntu2linaro1_armel.deb"
[11:42] <suihkulokki> I'll throw backport of gzip to the ppa
[11:43] <kalikiana> infinity: same error
[11:44] <infinity> kalikiana: Oh, right.  "rm /usr/share/doc/libbz2-1.0/changelog.Debian.gz && dpkg -i /var/cache/apt/archives/libbz2-1.0_1.0.5-6ubuntu2linaro1_armel.deb"
[11:44] <infinity> kalikiana: That'll make it happy. :P
[11:45] <kalikiana> evil :-D let's try
[11:45] <kalikiana> you won't believe, same error
[11:46] <infinity> Err, that's not possible.
[11:46] <infinity> Or, shouldn't be.
[11:46]  * ogra_ wonders how that cross build setup is set up ... might be caused by that
[11:46] <infinity> ogra_: No, it's just straight up multiarch and gzip sadness, I'm sure.
[11:47] <ogra_> weird
[11:47] <infinity> But deleting the target before installing the other arch's package should work...
[11:47] <infinity> kalikiana: It's not complaining about another file now, perhaps?
[11:47] <ogra_> kalikiana, seriously, how many days did you spend on getting that working now ?
[11:47] <kalikiana> presumably "different" here includes that it exists
[11:48] <kalikiana> ogra_: I had a different setup before that, native arm, wither other problems. although I could get it to sort of work, it wasn't exactly working well
[11:48] <kalikiana> it took in the hour range to test anything
[11:50] <ogra_> well, the build only takes 12h
[11:50] <ogra_> at least the lsat successfull one in the archive did
[11:50] <ogra_> given that you alkready spent several days to get your cross setup working ...
[11:51] <kalikiana> it was not 12h, more like 2h, but still, that's no basis for working on code
[11:52] <ogra_> 2h ? for a plain make you mean, surely not for the package build (natively)
[11:52]  * infinity decides to refrain from "when I was your age" stories.
[11:52] <ogra_> haha
[11:53] <kalikiana> ogra_: when I say native I mean chroot. which I guess is faster, but still a pain
[11:53] <infinity> Besides, if you're "working on code", you don't rebuild from scratch every time, you have a built tree, and you let the magic of make only re-compile and re-link the bits you changed.
[11:53] <ogra_> right
[11:53] <ogra_> and that should just take minutes
[11:53] <ogra_> unless you make clean every build
[11:53] <kalikiana> infinity: unfortunately it includes changing the build system
[11:54] <infinity> Fun.
[11:54] <kalikiana> yes. plenty.
[11:54] <infinity> Speaking of build systems.
[11:55] <infinity> I'm grumpy that I need to teach fpc about armhf after all. :/
[11:55] <ogra_> give it to NCommander :P
[11:55] <ogra_> he did it several times before
[11:55] <infinity> Because, despite not being VFP-aware, it DOES hardcode the linker path when linking with C code.
[11:55] <ogra_> and doesnt have libO anymore on his plate .... he needs a new challenge
[11:57] <infinity> suihkulokki: Say, about LibreOffice...
[11:58] <suihkulokki> infinity: looks like janimo is ahead of me..
[11:59] <infinity> Oh, I didn't realise Jani was working on it too.
[11:59] <infinity> Hrm.
[11:59] <infinity> Duplication of effort, for the loss.
[12:00] <suihkulokki> ogra_: I could always tell people to use ebuilds when they want to cross-compile ;)
[12:00] <micahg> infinity: any idea how to bootstrap gnat-4.6?
[12:00] <infinity> micahg: Cross-compile from another arch, native compile and check for correctness.
[12:01] <infinity> micahg: markos was working on it, and seemed to be stuck on the latter step.
[12:01] <micahg> infinity: right, but how to do for the archive, same?
[12:01] <ogra_> suihkulokki, lol
[12:02] <infinity> micahg: Cross, native, plunk native in my stage-2 repo of doom, build on buildds.
[12:03] <micahg> infinity: ah, cool, ok, that's what I thought which is why I can't do it :)
[12:03] <infinity> micahg: If you can get the first two steps done, I won't mind. :P
[12:03] <janimo`> \o/ libreoffice passes the bridge tests on armhf, on to the rest of the build
[12:03] <infinity> micahg: If you give me a self-hosting gnat, I'll happily turn it into something archivey.
[12:03] <infinity> janimo`: !
[12:04] <janimo`> infinity, !
[12:04]  * janimo` does not let himself be intimidated by excalmation marks
[12:04] <ogra_> janimo`, !!!!
[12:04] <ogra_> !
[12:04] <infinity> Hahaha.
[12:04]  * janimo` collapses
[12:04] <xranby> janimo`: !o!
[12:05] <infinity> janimo`: That's awesome news.  And I suspect awesome news for suihkulokki, who now doesn't have to care. :P
[12:05] <janimo`> infinity, yep. I just need top make sure it works on OABI - the code still has that support although I am not sure who still cares
[12:06] <janimo`> xranby, is that the 'happy drummer' sign?
[12:06] <infinity> janimo`: Pardon my French, but fuck OABI.
[12:06] <infinity> janimo`: If anyone's building Open/LibreOffice for OABI, they should be shot.
[12:06] <janimo`> infinity, my thoughts exactly only I express them more delicately
[12:07] <janimo`> I was not sure how much Debian cares about baxckporting TBH, I am not sure either how much of Debian users are on legacy hw/installs
[12:07] <infinity> janimo`: More to the point, while an upstreamable fix might need to keep OABI working (though, god knows why), a Debian/Ubuntu patch clearly doesn't.
[12:08] <janimo`> I plan on pushing upstream today
[12:08] <janimo`> and deal with bug reports if OABI people come along
[12:08] <infinity> janimo`: Debian doesn't support OABI.
[12:08] <suihkulokki> OABI is forgotten in debian. however we should check it doesn't break EABI softfloat
[12:08] <janimo`> I'll put ifdef around FP regs usage and that should be all I guess
[12:08] <infinity> suihkulokki: EABI soft, or softfp?
[12:08] <janimo`> suihkulokki, test passes on armel as well
[12:08] <janimo`> but only hardfloat tested
[12:08] <infinity> (God, that's confusing)
[12:09] <infinity> janimo`: Our armel is softfp, which is still VFP-aware.
[12:09] <janimo`> I have no soft (no FPREGS usage at all) setup
[12:09] <infinity> janimo`: Debian's armel isn't.
[12:09] <infinity> And somewhere along the way, my head explodes.
[12:09] <janimo`> aha, that indeed needs to be checked for, I'll make use of the SOFTFP define then and hope it is not too much work
[12:11] <janimo`> infinity, suihkulokki can I test a Debian/softfloat setup in an ubuntu hosted chroot ? just create a sid-armel one?
[12:11] <suihkulokki> janimo`: yes
[12:11] <janimo`> schroot I mean if it matters
[12:11] <janimo`> oh great then
[12:12] <infinity> janimo`: Yeah, kernels are completely VFP agnostic, so debian-armel chroots work fine.
[12:12] <infinity> (And armhf, and, and)
[12:13] <janimo`> excellent
[12:14] <suihkulokki> janimo`: didn't you ifdef the hardfb abi with__ARM_PCS_VFP already? that should not be set on either debian or ubuntu armel
[12:14] <janimo`> suihkulokki, yes that one I used
[12:14] <janimo`> but I noticed there's another SOFTFP variable too
[12:14] <janimo`> so it may all just work indeed
[12:14] <infinity> Which may or may not relate to softfp.
[12:14] <ogra_> hardfb ? hard floating bubble ?
[12:15] <infinity> Because the soft/softfloat/softfp naming between toolchain and userspace applications is never consistent. :P
[12:15] <infinity> (Heck, it gets even worse when Oracle refers to softfp as "hard-float")
[12:15] <xranby> heh yes.
[12:15] <ogra_> haha
[12:15] <infinity> And they're not wrong.  It is hard float.  Just not what WE call hard float.
[12:16] <xranby> its kind of funny oracle compared their tuned armel builds against icedte built using debian squeeze
[12:16] <ogra_> could have been worse
[12:16] <ogra_> they could have built against woddy
[12:17] <infinity> We didn't have armel in woody, did we?
[12:17] <ogra_> nah
[12:17] <infinity> woody would have been OABI, I believe.
[12:17] <ogra_> only arm i think, if at all
[12:17] <infinity> But it's been a while.
[12:18] <xranby> i think we are doing good, at least our work runs on the armhf ABI
[12:19] <infinity> I dunno.  I gnored all you ARM weirdos back then.  I was working on promising new future technologies like m68k and parisc.
[12:19] <ogra_> mips ?
[12:19] <infinity> I wasn't a mips porter, no. :)
[12:20] <infinity> 68k, parisc, powerpc, and alpha.  I sure can pick 'em.
[12:20] <infinity> 1 out of 4 isn't bad, right? :P
[12:21] <ogra_> mmm, alpha ... i loved them
[12:21]  * janimo` completely forgot how he created the precise-armhf schroot, now needs to figure out same for debian.sigh
[12:21] <janimo`> I do not recall running debootstrap explicitly
[12:21] <janimo`> and my bash history agrees
[12:21] <janimo`> it may have been mk-sbuild
[12:22] <infinity> janimo`: debootstrap --variant=buildd --arch=armel sid sid-armel http://ftp.debian.org/debian
[12:22] <infinity> janimo`: Ish?
[12:22] <janimo`> yes, it was not that I guess, probably mk-sbuild did it all behinf the curtains for me
[12:23] <janimo`> do debootstrap and schroot have a common location for chroots in which case I may just do that above
[12:23] <janimo`> mk-sbuild --eatmydata --arch=armel precise was it
[12:25]  * janimo` remembers seeing the one and only alpha machine sometime in 94 at an expo. It was higher Mhz that the 486's (150 I think) and it had a video promo of Jean Luc Picard extolling its virtues
[12:26] <janimo`> probably they though it was meant for enterprise servers
[12:26] <infinity> janimo`: debootstrap has no canonical location for anything, it just creates the chroot where you tell it to.
[12:27] <janimo`> infinity, ok I just started a mk-sbuild so it is stored along with the rest of schroots
[12:28] <suihkulokki> perhaps I can do the debian/armel build and testing
[12:29] <janimo`> suihkulokki, sure thanks. I am setting up a sid chroot now but my panda would be happier if left to build only a precise armhf and not something else in parallel :)
[12:32] <suihkulokki> janimo`: ok, on it
[12:36] <janimo`> suihkulokki, softfloat in debian mean no actual VFP instructions in asm right? Not that they are trapped and emulated by the kernel
[12:41] <janimo`> suihkulokki, you can stop the build after a couple of hours (not sure when) once the deps for bridges/ and testtools/ are built.
[12:41] <janimo`> then make bridges.deliver testtools alternating with changes to code is easy iteratin
[12:42] <suihkulokki> janimo`: do you have a line to grep in the buildlog when bridges have compiled?
[13:04] <janimo`> suihkulokki, hmm, not sure I know where the bridges' module number is
[13:04] <janimo`> what I did was ctrl-c and see if make brdiges works or says it has files missing
[13:05] <janimo`> but  gcc3_linux_arm is a dir within bridges that needs to be entered so maybe good for grepping
[13:11] <janimo`> last build of libo on armel in the buildd: 5 days 19 hours. Ouch
[13:11] <infinity> janimo`: On a babbage, I assume?
[13:12] <janimo`> assuming a panda is used instead of babbage it still likely be 1-2 days
[13:12] <janimo`> infinity, yes some old board
[13:12] <janimo`> I think with pandas it was over a day too last cycle
[13:12] <janimo`> or whenever we had pandas built libo
[13:12] <infinity> Yeah, a dayish sounds about right.
[13:12] <janimo`> by accident
[13:12] <janimo`> so I am not holding my breath today for it to complete
[15:06] <jeremiah> .c
[15:48] <slangasek> infinity: actually, the test suite failure I was fixing in upstart was unrelated... the one on arm*/ppc is still there, and I'm not sure what to make of it
[15:52] <infinity> slangasek: Oh, it just happens to be in the same test.  But, you're right, different error.
[16:12] <slangasek> infinity: yes, the "same", 4kloc test ;)
[16:16] <infinity> slangasek: Ugh.
[16:27] <kalikiana> suihkulokki: did you upload updates for libbz2 or gconf2 yet?
[16:36] <suihkulokki> kalikiana: yes but bzip2 is still building
[16:56] <pbuckley> this morning's dump of updates seems to have another alsa bug
[16:56] <pbuckley> ALSA lib conf.c:1220:(parse_def) show is not a compound
[16:56] <pbuckley> ALSA lib conf.c:1686:(snd_config_load1) _toplevel_:24:26:Unexpected char
[16:56] <pbuckley> ALSA lib conf.c:3406:(config_file_open) /usr/share/alsa/pulse-alsa.conf may be old or corrupted: consider to remove or fix it
[16:57] <pbuckley>                 show {
[16:57] <pbuckley>                         @func refer
[16:57] <pbuckley>                         name defaults.namehint.basic
[16:57] <pbuckley>                 }
[17:34] <slangasek> infinity: ah, I understand jhunt has figured out the race in the test that was causing things to fail, so we should have a fixed package tomorrow-ish
[17:34] <infinity> slangasek: \o/
[18:17] <orion___> ALLCON:  I am attempting to setup ubuntu server 11.10 on a Pandaboard es with no luck.  I attempted multiple times with the same pre-installed distro with different outcomes. They range to when the system unpacks and reboots, I either booting and then nothing, booting and then root access.  With root access I try to adduser and get one of two options:  The user is added but not in the sudoers list, or the user is not added and I
[18:18] <orion___> I gave up for a while and tried installing 12.04 and had no issues at all.  It went straight to the installation screen, gave me all my options, and then worked great.  I just went back to 11.10 since it is supported
[18:18] <orion___> Is there anyone who may know what is wrong and could help
[18:18] <GrueMaster> orion___: 11.10 doesn't have full support for the 4460 in u-boot or kernel.
[18:19] <GrueMaster> It can cause overheating.
[18:19] <orion___> is there a better option to go with
[18:19] <GrueMaster> I am testing 12.04 daily.  It is very stable, but since it is in development, constantly updating stuff.
[18:20] <GrueMaster> You should be fairly safe running Alpha 2, then upgrading during milestones (beta 1, 2, etc).
[18:20] <orion___> yeah, this is going onto a robot that needs to be mostly stable.  I will only need usb, ethernet, wireless (maybe bluetooth), and the ability to work with the gpio if needed
[18:21] <GrueMaster> Ah.  Yea, stick with the 12.04 and just turn off auto-updating.
[18:21] <orion___> How are the service packages with 12.04.  For instance, I tried to download openjdk as a quick test with 12.04 and couldnt find it
[18:22] <GrueMaster> It is there.  I use it daily to run a Jenkins slave.  I use open-jdk-jre-headless, but I also just tried default-jdk.
[18:22] <orion___> got it
[18:23] <orion___> just must have missed it then
[18:23] <GrueMaster> default-jdk will give you a lot more packages, but only really usefull cor compiling java.
[18:23] <GrueMaster> /cor/for
[18:23] <orion___> and would you say that 12.04 server is the fastest build for pandaboard es right now?
[18:24] <GrueMaster> Yes.  Especially the armhf release.  BTW, we will no longer be making armel images after today.
[18:25] <pbuckley> orion___: i will voice for 12.04 armhf builds be wicked fast
[18:25] <orion___> got it.    I will go back to 12.04 then
[18:26] <pbuckley> (though slap a hard drive on the thing.. running off the sd card is pure pain)
[18:26] <orion___> yeah, that is another area I am noticing
[18:26] <pbuckley> Linux panda 3.2.0-1406-omap4 #8-Ubuntu SMP PREEMPT Tue Feb 14 16:12:38 UTC 2012 armv7l armv7l armv7l GNU/Linux
[18:26] <orion___> thinking of getting an ssd
[18:26] <pbuckley> here is what i did
[18:26] <pbuckley> LABEL=home /home ext4 defaults,noatime,errors=remount-ro 0 0
[18:26] <pbuckley> LABEL=usr /usr ext4 defaults,noatime,errors=remount-ro 0 0
[18:26] <pbuckley> LABEL=var /var ext2 defaults,noatime,errors=remount-ro 0 0
[18:26] <pbuckley> tmpfs /tmp tmpfs defaults,noexec,nosuid 0 0
[18:26] <pbuckley> tmpfs /var/log tmpfs defaults,noexec,nosuid 0 0
[18:26] <pbuckley> tmpfs /var/run tmpfs defaults,noexec,nosuid 0 0
[18:26] <pbuckley> tmpfs /var/lock tmpfs defaults,noexec,nosuid 0 0
[18:27] <pbuckley> though ill probably migrate /var/log to the hard drive
[18:27] <pbuckley> i had it in a ramdisk before i added the hd
[18:27] <orion___> got it
[18:28] <pbuckley> GrueMaster: btw it looks like that sound patch made it in the recent kernel build \o/
[18:28] <orion___> thanks to both of you
[18:28] <GrueMaster> for your robot usage, SD should be fine.  It really only sucks when you have a lot of io load.
[18:28] <pbuckley> (by a lot he means more then 2 MB/s
[18:28] <GrueMaster> pbuckley: Yes, I was told today.  Also fixed the ucm configs last week.
[18:28] <pbuckley> )
[18:28] <orion___> the robot will be communicating with the google cloud and with other robots
[18:28] <pbuckley> indeed.. there is a new alsa bug i mentioned earlier
[18:28] <pbuckley> but it doesnt break functionality
[18:28] <GrueMaster> sounds cool.
[18:28] <pbuckley> just throws a warning
[18:29] <pbuckley> orion___: sweet.. graduate project?
[18:29] <orion___> also, may be using opencv, so there is a bit of IO
[18:29] <GrueMaster> pbuckley: I'll look into it.
[18:29] <orion___> pbuckley: yes
[18:29] <pbuckley> reminds me of
[18:29] <pbuckley> http://www.google.com/url?sa=t&rct=j&q=ryan%20walker%20robot&source=web&cd=1&ved=0CCYQFjAA&url=http%3A%2F%2Fweb.cs.swarthmore.edu%2F~meeden%2Fcs81%2Fs09%2Ffinals%2FRyan.pdf&ei=Eks9T4H4AuTUiALj-dzDAQ&usg=AFQjCNG3THVik7wByH61j67PnDqGDWn2Ww&cad=rja
[18:30] <orion___> pbuckley: pioneer robots?
[18:32] <orion___> pbuckley: same ideas.  Going to be multiple ground and air vehicles cooperating togehter
[18:32] <orion___> *together
[18:32] <pbuckley> if you want me to hook you up with that author of that paper hes usually interested in talking about robots ;)
[18:33] <orion___> that's be great, however this wont be my common irc name.  Using webirc now, working on setting up a more permanent version right now
[18:37] <orion___> strange
[18:37] <orion__> pbuckley: think i got it setup
[18:39] <orion__> pbuckley: yeah, looking at the paper, it seems pretty good with the adaptive controls
[18:40] <GrueMaster> orion__: When you start diving into this on the panda, I recomment you keep a complete copy of your workspace on your desktop that you can just dump into the SD after flashing a new image.  It is much faster to flash a fresh image than it is to update on SD.
[18:41] <orion__> GrueMaster: do you mean a complete copy of code, etc.  I haven't moved anything to the distro yet.  I am currently getting the board setup first to move code from a chumby hacker board
[18:43] <GrueMaster> Yes.  What I do with my test projects is store them in a self-contained tarball,  When I run them, I assume a clean image and install the necessary packages, change the environment settings, etc accordingly.
[18:44] <GrueMaster> Too often someone on here complains that they lose a lot of work when they decide to upgrade and they are on SD.
[18:44] <GrueMaster> I prefer to think of the SD as a good demo image/embedded project storage that is volatile.
[18:45] <orion__> I see what you are saying.  I will be working on setting up a cross compiler environment on my laptop soon.  I will then be holding my projects both on the laptop and pandaboard so that shouldnt be a problem
[18:46] <GrueMaster> Can't wait to see your project on youtube.  :P
[18:47] <pbuckley> orion__: distcc is also fun
[18:47] <orion__> me too.  We already have 6 ground vehicles working well.  Working on building 2 quadcopters at the moment, but those won't be done until the beginning of summer
[18:49] <orion__> Anways, I don't want to tie up the board.  I appreciate both of your help.
[18:50] <pbuckley> come back soon ;)
[18:50] <orion__> I'll be hanging out.  Still have to see if this goes smoothly
[18:50] <pbuckley> :D
[18:51] <orion__> and the download for 12.04 is going very slow today
[18:55] <Epsilonorion> pbuckley: This will be my main name if I am on
[18:58] <pbuckley> alright.. ill let him know.. he's in the zone tippity tapping
[18:58] <Epsilonorion> GrueMaster: Actually one question.  Should I download the current daily build or the alpha 2 version the channel provides a link for
[18:59] <GrueMaster> Either or.  The daily-preinstalled has a newer kernel with some fixes, mainly for audio.
[19:00] <Epsilonorion> ok, then I will stick with that one.  Thanks again
[21:25] <GrueMaster> Ooo, new shiny.  http://makeplaylive.com/
[21:27] <GrueMaster> Price and specs are comparable to a Nook Tablet.  More usb ports and a camera as well.