[00:15] <scientes> ATP you said LVDO which isn't usb
[00:16] <scientes> try tail -f /var/log/kern.log and the unplug and replugin the device
[02:09] <GrueMaster> TheMuso: I would assume so.  The alsa issue on panda was pretty much resolved with my patch to the ucm configs and a kernel patch.  Unfortunately, we didn't have images for a week, so I only spotted it Friday.
[02:17] <TheMuso> GrueMaster: Right, well I did announce a call for testing for alsa-utils, I know the ubuntu-audio-dev PPA is not building for ARM atm, but I thought you guys would have seen the cft, pulled and rebuilt at least...
[02:39] <twb> TheMuso: I have a TF101, I remember there was a problem with oneiric's alsa-utils and I fixed it by cherry-picking precise's...
[02:40] <twb> Something festival was triggering
[02:40] <twb> Probably unrelated, so ignore me and carry on
[06:15] <pnphi> joined
[06:16] <pnphi> help me
[06:16] <pnphi> ERROR: An error occurred while enabling: mailmerge.py Cause: (com.sun.star.registry.CannotRegisterImplementationException) { { Message = "ImplementationRegistration::registerImplementation() InvalidRegistryException during registration (destination registry is read-only!  cannot merge!)", Context = (com.sun.star.uno.XInterface) @0 } }  unopkg failed.
[06:16] <pnphi> what errors ??
[06:16] <twb> I don't even want to look at that
[06:18] <pnphi> ERROR: An error occurred while enabling: mailmerge.py
[06:18] <pnphi> Cause: (com.sun.star.registry.CannotRegisterImplementationException) { { Message = "ImplementationRegistration::registerImplementation() InvalidRegistryException during registration (destination registry is read-only!  cannot merge!)", Context = (com.sun.star.uno.XInterface) @0 } }
[06:18] <pnphi> unopkg failed.
[06:24] <micahg> ok, uploading chromium which will hopefully build on armhf
[06:25] <pnphi> udo rootstock \         --fqdn ubuntu \         --login ubuntu \         --password ubuntu \         --imagesize 3G \         --seed ubuntu-desktop
[06:25] <pnphi> this command ! !
[06:29] <twb> I thought rootstock was deprecated
[06:30] <pnphi> hjx
[07:50] <infinity> micahg: \o/
[07:50] <micahg> it's started to compile, it's not on a panda, so it might be another 17 hours until we know for sure if it worked
[07:50] <infinity> Err, what?
[07:50] <infinity> Grr.
[07:50] <infinity> Who took the beagles off manual? >:(
[07:51] <micahg> they've been off manual all weekend
[07:53] <infinity> micahg: Not true.
[07:53] <micahg> well, since sat night my time AFAIR
[07:53] <twb> infinity: that beagles line took me *way* too long to understand
[07:53] <infinity> micahg: Looks like they only went off manual about 5h ago.
[07:54] <infinity> micahg: Anyhow, hleoung fessed up to it at least.  Maybe I'll get your builds killed.
[07:54] <micahg> well, they were rebalanced apparently about that time as well
[07:54] <micahg> infinity: sounds good to me :)
[07:55] <infinity> micahg: No, I rebalanced and put them on manual around a day ago.
[07:55] <infinity> micahg: Keep up. ;)
[07:55] <micahg> ah, ok :), I slept at some point in there, so it's all blurring together :)
[07:56] <infinity> Pfft.  "sleep"?
[08:01] <infinity> micahg: I notice that firefox hates PPC again. :/
[08:02] <micahg> yeah, upstream is fighting about it :)
[08:02] <infinity> Fun.
[08:03] <twb> IME mozilla hates everyone
[08:05] <micahg> nah, it's just the JIT components change frequently and powerpc isn't a tier 1 platform, so there's no check if it breaks when stuff is committed
[08:45] <micahg> infinity: crud, armhf failed, seems like missing libc headers which is worrysome: https://launchpadlibrarian.net/93446095/buildlog_ubuntu-precise-armhf.chromium-browser_17.0.963.56~r121963-0ubuntu3_FAILEDTOBUILD.txt.gz
[08:51] <infinity> micahg: That seems... Odd.
[08:52]  * infinity digs deeper.
[08:53] <infinity>  /usr/include/arm-linux-gnueabihf/bits/predefs.h
[08:53] <infinity> Looks there to me...
[08:53]  * infinity upgrades linux-libc-dev to see if it went poof.
[08:53] <micahg> right, I thought it was odd
[08:54] <infinity> micahg: Does chromium do anything suspect with toolchains, like zero out and rewrite the standard include paths?
[08:54] <infinity> micahg: (And maybe get it wrong for armhf?)
[08:54] <micahg> I can't say a definite no to that, it's possibke
[08:54] <micahg> *possible
[08:54]  * micahg checks the Debian patch
[08:57] <micahg> Debian's stuff is still building, but they don't seem to do any path hacking
[08:57] <infinity> Well, predefs.h exists in the same place on amd64 and armhf (except for the triplet, of course)
[08:58] <infinity> So, about the only way this could go wrong is a multiarch/triplet goof.
[08:58] <infinity> And if the armhf toolchain was broken, you surely wouldn't be the only package failing.
[08:58] <infinity> Or, one would think not. :P
[09:00] <infinity> Eww, chromium is cdbs?
[09:01] <micahg> not my choice and I'm too lazy to rewrite it
[09:01] <micahg> # BUILD_ARGS=SYMBOLS=1 BUILDTYPE=Release CFLAGS="" CXXFLAGS="" CPPFLAGS="" LDFLAGS="" -j3
[09:01] <micahg> that would be the only thing I can think of
[09:04] <infinity> I hate build systems that obfuscate the compiler command line. :/
[09:04] <infinity> But I have a sneaking suspicion there's some -nostdinc action going on there.
[09:04] <infinity> And then manual reconstruction of stdinc.
[09:04] <infinity> For no sane reason.
[09:04] <infinity> But that's just a wild guess.
[09:09]  * infinity boggles.
[09:09] <infinity> Why does the chromium source contain pre-compiled compilers?
[09:09] <infinity> I think I just vomited a little.
[09:18] <infinity> micahg: Tell me none of this bundled stuff (like ffmpeg) is included in the build?
[09:19] <micahg> infinity: umm, it shouldn't be using any of them
[09:19] <infinity> Kay.  Just checking.
[09:19] <infinity> Cause it makes some radical assumptions about arm=softfp.
[09:20] <micahg> google ships their own toolchain for nacl, but I can't get it to build yet
[09:20] <infinity>   // Ubuntu 11.10 (Oneiric) places the libraries here.
[09:20] <infinity> #if defined(ARCH_CPU_X86_64)
[09:20] <infinity>   paths.push_back(FilePath("/usr/lib/x86_64-linux-gnu/nss"));
[09:20] <infinity> #elif defined(ARCH_CPU_X86)
[09:20] <infinity>   paths.push_back(FilePath("/usr/lib/i386-linux-gnu/nss"));
[09:20] <infinity> #elif defined(ARCH_CPU_ARMEL)
[09:21] <infinity>   paths.push_back(FilePath("/usr/lib/arm-linux-gnueabi/nss"));
[09:21] <infinity> #endif
[09:21] <infinity> ^-- Might relate to our issue.
[09:21] <infinity> crypto/nss_util.cc
[09:21] <micahg> yep, the multiarch path hack
[09:21] <micahg> I remember that now
[09:22] <infinity> But, still, unless they're using that file to then define their include paths for the compiler, I don't see how it being incorrect/incomplete would lead the the build failure.
[09:22] <infinity> But, again, obfuscated build log means I have no effin' idea what it's doing. :/
[09:22] <infinity> I might have to do a local test build tomorrow.
[09:23] <infinity> Or you could do it on scheat.
[09:24] <micahg> yeah, that doesn't seem to make sense for this failure though
[09:24] <infinity> And none of the native_client/tools/llvm stuff gets used, right?
[09:24] <infinity> Cause it's wildly in need of learning about armhf.
[09:25] <micahg> no
[09:25] <micahg> native_client is NaCL which is disabled on all archs ARM
[09:25] <infinity> Hrm.
[09:26] <micahg> that snippet you gave will cause a runtime issue on armhf though
[09:26] <infinity> Certainly, yeah.
[09:27] <infinity> Other than that, though, I can't find anything obviously broken outside native_client and third_party...
[09:28] <micahg> I guess I can kick off a build when I start tomorrow on scheat and poke a little
[09:29] <micahg> err, later today
[12:26] <pnphi> help me ...
[12:27] <pnphi> what the error ?
[12:28] <pnphi> An error occurred while enabling : mailmerge.py
[12:28] <xranby_ac100> pnphi: no-one uses rootstock    the last release was from 2010-08
[12:29] <pnphi> and unopkg failded
[12:29] <xranby_ac100> pnphi: do the ubuntu install images work on your board?
[12:29] <pnphi> and unopkg failed
[12:29] <pnphi> on qemu
[12:30] <pnphi> sudo rootstock \         --fqdn ubuntu \         --login ubuntu \         --password ubuntu \         --imagesize 3G \         --seed ubuntu-desktop
[12:30] <pnphi> i run the command
[12:30] <xranby_ac100> pnphi: why do you use rootstock?
[12:30] <pnphi> i see on the Wed
[12:30] <pnphi> so i use this
[12:31] <xranby_ac100> its not anything that are supported officially
[12:31] <pnphi> From step --> Setting up xulrunner-1.9.2 .... this process stop
[12:32] <pnphi> so what do i use ?
[12:32] <xranby_ac100> pnphi: people use ubuntu.core
[12:32] <xranby_ac100> ubuntu-core
[12:32] <pnphi> what is ubuntu-core ??
[12:33] <pnphi> this can create the image ubuntu for ARM
[12:35] <xranby_ac100> pnphi: the reccomended way to install ubuntu on arm are to use the release images
[12:35] <pnphi> i want to know...how to create this image
[12:36] <xranby_ac100> pnphi: please read https://wiki.ubuntu.com/Core
[12:38] <xranby_ac100> pnphi: rootstock that you tried to use are depricated and no longer maintained
[12:38] <xranby_ac100> pnphi: see https://wiki.ubuntu.com/ARM/RootStock
[12:39] <pnphi> help me..how use the ubuntu-code to make the image ubuntu for ARM
[12:39] <pnphi> i run on Qemu
[12:39] <xranby_ac100> you can also use live-build
[12:40] <pnphi> clearly ? ?
[12:40] <pnphi> link or Document ?
[12:42] <xranby_ac100> pnphi: http://live.debian.net/manual
[12:42] <xranby_ac100> pnphi: ubuntu uses live.build to build all its live-images
[12:43] <xranby_ac100> you can install the tool by running apt-get install live-build
[12:45] <pnphi> does this link help me to create the image ?
[12:45] <xranby_ac100> pnphi: sorry i cant help you further since i only use the live images produced and uploaded to http://cdimage.ubuntu.com/daily-preinstalled/current/
[12:45] <xranby_ac100> pnphi: yes it do
[12:47] <pnphi> ok thank you so much
[12:47] <pnphi> can i give your email ?
[12:47] <xranby_ac100> pnphi: so in a nutshell if you want to be able to create your own image identical to how ubuntu produce their images you will have to learn how to use live.build
[12:47] <xranby_ac100> no
[12:47] <xranby_ac100> please ask questions here
[12:47] <pnphi> yes
[12:47] <xranby_ac100> there are probably other developers who know live-build better
[12:48] <xranby_ac100> than I
[12:48] <pnphi> i want to create the image ubuntu desktop for ARm,run on Qemu ! ! !
[12:49] <pnphi> so..i learn from this link
[12:49] <pnphi> thank you
[12:50] <xranby_ac100> youre welcome
[13:05] <pnphi> so hard ! ! !
[13:06] <xranby> pnphi: https://wiki.linaro.org/LiveHelper/Hacking     try this linaro guide
[13:07] <xranby> pnphi: linaro use live-build to build a lot of arm images
[13:07] <pnphi> wow..thank you so much
[13:08] <pnphi> why rootstock deprecated ?
[13:09] <xranby> pnphi: because debian and ubuntu use live-build
[13:09] <xranby> to build their daily images
[13:10] <xranby> i really do not know any specifics
[13:10] <pnphi> wow..yes,
[13:13] <pnphi> thanks xranby
[13:13] <pnphi> i try ! ! !
[14:11] <berco> ndec_: j'ai pushé libdrm, libdri2 et xf86-video-omap dans omap trunk. je crois que tu en avais besoin. both armel et armhf builds
[14:11] <berco> ndec_: pour pvr, je bosse avec Xavier dessus
[14:11] <berco> ndec_: ha yes
[14:12] <berco> ndec_: nevertheless, you get the info ;)
[14:12] <ndec_> fortunately i speak french ;-)
[14:21] <gildean> google does too
[17:38] <ATP> does anyone know how i can change my dvimode? I tried uenv.txt already...
[17:40] <ppisati> GrueMaster: bug 937051
[17:40] <ubot2`> Launchpad bug 937051 in linux-ti-omap4 "Cannot set MAC address via kernel boot parameters" [Undecided,New] https://launchpad.net/bugs/937051
[17:58] <ATP> if anyone answered please say again , my browser crashed >.<
[18:53] <royale1233> hi
[18:54] <royale1233> hi
[20:59] <Epsilonorion_> Does anyone know of the best way to setup wireless ad-hoc within ubuntu server.  I attempted to edit the interfaces file (all in CLI) and haven't had any luck.  The network is being created because I can see it via another computer, however I cannot ping from the computer
[22:31] <gandhijee_> because i am trying to build some packages for ubuntu 10.04 on inside by ubuntu 11.10 chroot to 10.04
[22:31] <gandhijee_> and it doesn't build it the same as my 10.04 machines...
[22:33] <xranby_ac1001> gandhijee_: thats normal since all the build tools and compilers are newer in your chroot
[22:34] <gandhijee_> ? xranby i have a 10.04 chroot in my 11.10 build... i would expect i had the same tools as i do on my stand alone 10.04 inside of my 10.04 chroot.
[22:36] <xranby_ac1001> ok then i misunderstood you
[22:37] <gandhijee_> yeah, it is a bit confusing.
[22:37] <xranby_ac1001> well debug symbols inside binarys will contain the location of the sourcefiles that where used
[22:37] <xranby_ac1001> so binarys will not be 100% identical
[22:38] <xranby_ac1001> what kind of difference do you see?
[22:38] <gandhijee_> thats not really the problem.  when it goes makes the actual deb file, it get populated with different things.
[22:38] <xranby_ac1001> sounds like a bug for that package
[22:38] <gandhijee_> and i can't figure out why, as i tarred it from the actual system and moved it to the chroot and it doesn't work
[22:39] <gandhijee_> but i can untar it on the actual system in a different directory and it works.
[22:39] <xranby_ac1001> check the mount options inside the directory you untar it into
[22:40] <xranby_ac1001> a simple cross check that you do not have noexec bit set on the filesystem
[22:42] <xranby_ac1001> you can also run ldd on the binary to check that it got all shared librarys in place on the target system
[22:43] <gandhijee_> ok
[22:45] <xranby_ac1001> what kind of error do you see when you try to run the file onem?