[00:23] <slangasek> ScottK: does anything use the WTF_PLATFORM_IA64 define, then?
[00:23] <slangasek> ScottK: btw, bug #498631
[00:23] <ubottu> Launchpad bug 498631 in binutils "ld segfaults with --gc-sections on powerpc" [Undecided,New] https://launchpad.net/bugs/498631
[00:24] <ScottK> slangasek: Nothing except getting us into the JS64 set instead of 32_64
[00:25] <slangasek> oh, is that what the PLATFORM() macro expands to?
[00:25] <ScottK> More specifically WTF_USE_JSVALUE64 instead of WTF_USE_JSVALUE32_64
[00:26] <ScottK> The first patch I gave you would have resulted in using WTF_USE_JSVALUE64, but who knows what else.
[00:26] <ScottK> So I'm defining IA64 as an alternate way to get WTF_USE_JSVALUE64 without whaterver X86_64 might have brought along
[00:27] <ScottK> I'm pretty sure that's what I want to have happen, I'm really unsure it that's the way to do it.
[00:27] <ScottK> As I said earlier, I'm in over my head here.
[00:27] <slangasek> looks appropriate to me; should I try another ia64 build to see if anything else fails, or do you just want to throw this at the buildds along with the ppc fix?
[00:28] <ScottK> slangasek: Your call.  IA64 won't get more broken.
=== Hellow|Christmas is now known as Hellow
[01:16] <ScottK> slangasek: WRT timing, qt4-x11 takes a long time to build on armel.  We're packaging a new KDE upstream right now that's set for upload on Monday.  It'd be nice if qt4-x11 was not in the middle of building then, so I'd like to revise my answer and prefer an upload tonight.
[02:13] <ebroder> Suck. The open-vm-tools kernel modules apparently don't build on Lucid's kernel. Or Sid's
=== asac_ is now known as asac
[02:31] <LaserJock> where does Ubuntu Netbook Remix/Edition development happen?
=== Whoopie_ is now known as Whoopie
=== nhandler_ is now known as nhandler
=== nhandler_ is now known as nhandler
[07:57] <slangasek> ScottK: qt4-x11 has a completely broken clean target, btw
=== dendrobates is now known as dendro-afk
[14:01] <ScottK> slangasek: I see what's wrong with my patch.  I'll fix it.
[14:35] <fqh> Hi, all, which tool can be used to check linux kernel coding style? I forgot.
=== RainCT_ is now known as RainCT
[15:50] <ejat> anyone know how to temporary solve this bug 472345
[15:50] <ubottu> Launchpad bug 472345 in evolution "Evolution mail client completely closes when i click 'close window' from the 'File' menu. " [Wishlist,Invalid] https://launchpad.net/bugs/472345
=== tjaalton_ is now known as tjaalton
[18:06] <akgraner> ogasawara_, ping
[18:06] <zbert> Hello room... anyone in here?
[18:07] <zbert> I have some questions about #ubuntu-devel
=== ion_ is now known as ion
[18:08] <zbert> There's a lot of names in here but no one is in here?
[18:08] <geser> it's weekend so most are idle
[18:09] <zbert> okay, see that's one of my questions
[18:09] <zbert> isn't this an open source project?
[18:09] <zbert> Yesterday I got told to go to the #ubuntu room but isn't that like general support?
[18:09] <geser> yes, the Ubuntu distribution is open source
[18:09] <zbert> I'm wanting to participate in development in the same way that I do on source forge projects
[18:10] <zbert> Which being weekend thing confuses me as I do most of my coding on the weekend as I work my normal job during the week
[18:11] <geser> it depends, this channel is mostly used by the paid Ubuntu developers who seldom work on weekends
[18:11] <zbert> Yeah, see that's the answer I was looking for...
[18:12] <zbert> Where's a good place for the unpaid people who do open source as a hobby?
[18:12] <geser> #ubuntu-motu is where the "universe" community hang outs
[18:12] <zbert> It's been a pretty big downer because I was hoping to get involved with it more this weekend but I'm not really finding a good start point, maybe I'd do better working on the bugs
[18:13] <zbert> Haha... that's more the people like me who just want to do some systems coding
[18:13] <geser> have you been pointed to https://wiki.ubuntu.com/MOTU/GettingStarted already?
[18:13] <zbert> No, thanks... this is the help I've been looking for.
[18:14] <zbert> I'm not new to coding for open source but am new to doing it for Ubuntu so I just googled ubuntu development and got to here
[18:15] <geser> if you are interested in helping with Kubuntu, you might also want do look in #kubuntu-devel. The Kubuntu community is also very strong.
[18:17] <zbert> Yeah, but I barely tolerate KDE on Backtrack... I really prefer gnome or open-box
[18:17] <zbert> So I've not done much in working with KDE really... but I like hearing that.
[18:18] <geser> gnome is discussed in #ubuntu-desktop, but also mostly during the week
[18:18] <zbert> So #ubuntu-motu is more of what I'd be likely to find in working through something on like sourceforge/forge.mil type of projects?
[18:18] <zbert> Same situation, mostly done by the paid staff?  Curious, are you a paid staff?
[18:18] <geser> MOTUs care about the packages in the "universe" component of the archive
[18:19] <geser> gnome is mostly done by paid devs but also some community devs, and I'm not paid
[18:19] <zbert> Yeah, I was just reading that... I'm looking more to working with kernel programming and driver modules
[18:21] <zbert> Oh cool... I've always done programming as a hobby and never really thought of it as a pay thing, it's a big reward to see a patch or something I contributed on actually being applied.  I'm actually a social worker for my full time job
[18:21] <geser> the kernel people hang out in #ubuntu-kernel but I don't know how many paid/non-paid devs there are
[18:21] <zbert> Nice, I appreciate this tutorial to development in ubuntu, this helps a lot
[18:28] <zbert> So what projects do you work on?
[18:30] <ScottK> slangasek: No joy on powerpc, ld still bites: https://launchpad.net/ubuntu/+source/qt4-x11/4:4.6.0-1ubuntu5/+build/1407295/+files/buildlog_ubuntu-lucid-powerpc.qt4-x11_4:4.6.0-1ubuntu5_FAILEDTOBUILD.txt.gz
[18:41] <shtylman> is anyone else experiencing problems using intel 3945 wireless?
[18:41] <shtylman> are there any recent open bugs about it?
[18:41] <shtylman> (in lucid that is)
[18:50] <ogasawara_> akgraner: pong
[18:51] <akgraner> ogasawara_, is there a way to find total bugs ever reported for Ubuntu...on LP
[18:51] <akgraner> since the code push last week that number doesn't show up anymore
[18:51] <akgraner> :-(
[18:51] <akgraner> ogasawara_, here is where I normally got it from  https://launchpad.net/ubuntu/+bugs
[18:52] <ogasawara_> akgraner: hrm, was just going to point you to that, but if it's no longer there give me a sec and I'll see if I can find it
[18:52] <akgraner> ogasawara_, thank you!
[18:52] <ogasawara_> akgraner: https://bugs.edge.launchpad.net/ubuntu/+bugs?advanced=1
[18:53] <ogasawara_> akgraner: as a sort of brute force approach, go to the above and tick every status
[18:53] <zbert> hey, there are people in here... can I get some help finding my way around ubuntu development?
[18:53] <akgraner> ogasawara_, so just click all the boxes and it will give me a total
[18:53] <akgraner> well all the status'
[18:53] <zbert> I'd like to contribute, particularly to kernel and gui development, but I've not found rooms that are active
[18:53] <ogasawara_> akgraner: yah, tick all the status' (new, incomplete, etc. . .) and then hit search
[18:54] <akgraner> gotcha.. thank you!!!
[18:54] <zbert> like ubuntu-kernel is as quiet as this one... is there a decent place to go to get started contributing?
[18:54] <akgraner> ogasawara_, sorry to bug you on a Sunday...
[18:54] <ogasawara_> akgraner: np :)
[18:55] <zbert> akgraner or ogasawara_?
[18:55] <ogasawara_> zbert: it's the weekend so people are likely away.  is there a specific area you are interested in, for ex the kernel?
[18:56] <zbert> <zbert> I'd like to contribute, particularly to kernel and gui development, but I've not found rooms that are active
[18:56] <zbert> I'm just happy to find a foothold at this point
[18:57] <ogasawara_> zbert: well I'd be more than happy to get you started with the kernel
[18:57] <ogasawara_> zbert: a great place to initially lend a helping hand is triaging bugs
[18:57] <zbert> I figured for open source, weekends would be a good time but I've found that ubuntu development most be done a lot by paid staff...
[18:57] <ogasawara_> zbert: can you priv msg me your email and I'll send you some info to get started
[18:58] <zbert> Okay, sorry to appear frustrated, I've been reading through the pages then trying quiet rooms most of this weekend, and I only have time to code on the weekend as it's all hobby for me so a day and half of getting started has been used finding a foothold.
[18:58] <zbert> Sure, and thanks!
[19:30] <slangasek> ScottK: blast; ok, will look at why my powerpc patch doesn't work
[19:39] <ScottK> slangasek: Thank you.
=== nhandler_ is now known as nhandler
[19:48] <slangasek> ScottK: right; my patch doesn't work because I used another non-working bit in the build system as an example
[19:50] <slangasek> ScottK: are there docs for these .pro files anywhere?
[19:53] <ScottK> slangasek: I don't know.
[19:53] <ScottK> I usually just ask fabo about fixing qt4 stuff.
[19:53] <ScottK> Riddell: ^^^?
[19:57] <slangasek> ok.  I'm confident that the workaround in question is the correct one, I just have no idea how to apply it to powerpc given this .pro file format that I have no familiarity with
[20:02] <ScottK> Thanks.
=== yofel_ is now known as yofel
[20:25] <Lure> slangasek: .pro files are for qmake (from qt4)
[20:27] <Lure> slangasek: doc is here http://qt.nokia.com/doc/4.6/qmake-manual.html
[20:41] <slangasek> Lure: what does 'unix:!mac:*-g++*:' mean?
[20:55] <Lure> slangasek: to complex for my knowledge level ;-)
[21:14] <slangasek> Lure: ok, well, so far I haven't hit on the magic combination that lets me exclude powerpc from this
[21:34] <slacker_nl> hi, question, will grub-legacy be upgraded to grub2 by lucid? debian does this when going from stable to testing, will you do the same with karmic/hardy to lucid
[22:25] <wgrant> Laney: I've recreated the import that you retried, as bzr-svn this time. it worked: https://code.edge.launchpad.net/~wgrant/multidistrotools/trunk
[22:25] <Laney> wgrant: Cool. I just grabbed it from svn directly