[00:00] <scientes> GrueMaster, here: http://www.ubuntu.com/devices/android/features-and-specs
[00:00] <scientes> says chromium=default
[00:04] <GrueMaster> I really couldn't tell you.  There is a whole different team working on that stuff.
[00:04] <scientes> http://www.arm.linux.org.uk/docs/faqs/signedchar.php
[00:04] <scientes> so x86 uses signed char?
[00:05] <GrueMaster> But it is possibly due to chromium being already there for android.
[00:05] <scientes> ahh, yes they said synced bookmarks and history
[00:05] <scientes> so yes that is it
[00:09] <GrueMaster> As to the char issue, again I couldn't tell you.  I do know that the K&R C book (considered the C reference bible) does say that it could be either/or.  Proper coding standards recommend specifying the variable when creating it.
[00:10] <GrueMaster> I do remember this being an issue a long time ago between gcc and icc differences in behavior.
[00:15] <GrueMaster> The key to remember is that if you want your code to work across multiple platforms, never assume a default behavior to be the same.
[00:18] <infinity> Yeah, the signedness of char is very platform-specific (as in, arch + headers + moon phase)
[00:19] <infinity> Depending on it being either signed or unsigned is always a Very Bad Thing.
[00:19] <infinity> (And, really, treating chars as ints is deep voodoo and/or ignorance anyway, despite the underlying implementation of them as such)
[00:20] <GrueMaster> iirc, that was one of the first things covered in my C programming class.  And that was at a crap school.
[00:55] <infinity> janimo`: Bad news, libreoffice failed on armel and armhf.  (The armel failure doesn't look arch-specific; same thing happened on powerpc, but the armhf failure is testsuite-related, and only armhf)
[01:03] <steev> trying to build a kernel here, and i'm getting arm-linux-gnueabihf-ld command not found, and i can't seem to find the package that actually installs it (binutils *is* installed)
[01:04] <steev> this is on precise alpha2
[01:04] <steev> what i don't understand is that this is the armhf tarball, but it pretends like it's cross compiling
[01:09] <infinity> Maybe you need to sort out why it thinks it's cross-compiling, then.
[01:11] <GrueMaster> steev: What platform is this?  What image?
[01:19] <steev> GrueMaster:  precise-core-armhf.tar.gz (from alpha2)
[01:20] <GrueMaster> Ok.  On an arm system I would assume?
[01:20] <steev> it's on an i.mx51 machine, (i AM chrooted via a m
[01:20] <steev> mmm... whatever the M release was
[01:21] <steev> maverick
[01:21] <GrueMaster> ok.  Should work.  I can try to reproduce it here if you can give me some quick steps (not something like Build LibreOffice).
[01:24] <steev> GrueMaster: <partitiion sd card, tar -xpf precise-core-armhf, apt-get update, apt-get install ubuntu minimal (watch it fail because of resolvconf), apt-get install git-core, git clone git://github.com/genesi/linux-legacy.git, <edit sources.list, add universe> apt-get update again, apt-get install kernel-package build-essential <setup locales>, cd linux-legacy, mv .git .dotgit (this may be un-neces
[01:24] <steev> sary, but on some versions of ubuntu it would add a + which would screw things up because of the .git dir), cp arch/arm/configs/mx51_efikamx_defconfig .config, make-kpkg --uc --us --initrd --subarch efikamx --rootcmd=fakeroot --revision 2012.02 binary
[01:24] <twb> What does "ubuntu for android" actually mean?  Presumably it's just the GUI fluff, and not important stuff e.g. busybox, initramfs-tools, dpkg, apt ?
[01:27] <GrueMaster> twb: Essentially it means that with this package, when you plug your android phone into a dock with keyboard/mouse/monitor, it will launch an ubuntu chroot environment and display it on the monitor.
[01:27] <GrueMaster> Similar (but far more integrated) to the Motorola Atrix.
[01:30] <twb> Ah, OK, so it's a chroot.  And you can install it via the android market?
[01:32] <GrueMaster> twb: If you read the info on ubuntu.com, then you know as much as I do at this point.  :D
[01:33] <steev> GrueMaster: oh i left off the chroot part, but i guess you'd know that much :)
[01:35] <twb> I read LWN's repost :P
[01:35] <twb> I was gonna read the whole subscriber-only article but I've lost my LWN pasword and ICBF digging it out
[01:55] <scientes> twb, yeah looks pretty cool doesn't it
[01:55] <scientes> saw it in ln too
[01:55] <scientes> *lwn
[01:55] <twb> scientes: not really
[01:55] <scientes> well, then why are you asking about it?
[01:55] <scientes> its pretty simple
[01:55] <twb> I have zero respect for android; this addition seems notably only in that you get a chroot without having to jailbreak.
[01:55] <twb> scientes: I'm asking to confirm that it's not actually any sexier than I guessed
[01:55] <scientes> they did a little cool stuff like sync bookmarks and history
[01:57] <GrueMaster> I'm really not sure about this new product, but I would guess it is for integration in new devices and not generally publicly available.
[01:57] <GrueMaster> I.e, you have to buy a phone with this preloaded, or available in the market for that phone.
[01:57] <twb> GrueMaster: ah, so the idea is that Mr. Motorola or whoever goes "ubuntu is cool, this will add value to my upcoming WhizzBang 9000 device for little investment"
[01:57] <twb> Gotcha
[01:57] <GrueMaster> But the basic concept is not new.
[04:17] <steev> wth?
[04:17] <steev> debian/ruleset/arches doesn't have armhf in it
[04:23] <lilstevie> twb, from what I see it is just the same as webtop is on the motorola atrix
[04:24] <twb> lilstevie: I'm not familiar with that, but GrueMaster et al explained it to me a bit.
[04:24] <lilstevie> not quite a chroot
[04:25] <lilstevie> and it gets given /dev/fb1 (the hdmi port)
[04:45] <twb> It's interesting but I think I'd still prefer to just fuck off android completely, or at most dual-boot
[05:26] <steev> GrueMaster: i worked around it by adding in armhf by copying/editing the armel.mk (and making related entries into the other .mk files), no need to test
[05:27] <GrueMaster> steev: Excellent!  My wife had drug me off to dinner, I just got back (sorry).
[05:27] <steev> no worries
[05:27] <steev> i was playing WoW anyway
[05:35] <lilstevie> :/
[05:36] <lilstevie> I am having shutdown problems, screen goes blank, nothing happens, logs don't reveal anything :/
[05:52] <janimo`> infinity, checking. I should have started a package build myself right after it was uploaded so I have a FTBFS locally when needed. Oh well
[09:06] <janimo`> infinity, there is hope for libo armhf. According to the Debian maintainer the workaround of not building Base needs to be instated for armhf as it is for armel
[18:29] <steev> is there a way to force resolvconf to... configure?  since i'm in a chroot, it can't exactly start, and because of that it keeps throwing up errors
[18:32] <ogra_> steev, just copy /etc/resolv.conf from the host
[18:33] <steev> ogra_: i have that, i'm trying to install the package resolvconf
[18:33] <ogra_> do you have /proc mounted etc ?
[18:33] <steev> and since it can't start in the chroot it doesn't install successfully (it's a dependency for ubuntu-minimal)
[18:33] <infinity> Does 'initctl reload-configuration' help?
[18:33] <steev> ogra_: yes
[18:34] <infinity> Well, 'initctl reload-configuration && dpkg --configure -a'
[18:34] <infinity> (Really, chroots should have a policy-rc.d that just denies starting services, though)
[18:35] <steev> ill try when these packages finish installing, sdcards be slow
[19:50] <steev> infinity: start: Unknown job: resolvconf\ninvoke-rc.d initscript resolvconf, action start failed.\ndpkg: error processing resolvconf (--configure)
[21:28] <steev> ogra_: infinity: any other suggestions?
[23:01] <steev> infinity: ah, someone explained the policy-rc.d to me, okay, have it installed, now i just need to get it booting, thanks for the pointer