[06:19] <armin76> asac: g++ -march=armv5te -pipe -pthread -fno-exceptions -fvisibility=hidden -Wall -D_FILE_OFFSET_BITS=64 -m32 -fno-ident -fdata-sections -ffunction-sections -fno-asynchronous-unwind-tables -fomit-frame-pointer -O3 -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -DENABLE_LOGGING_AND_PROFILING -DENABLE_DEBUGGER_SUPPORT -D__STDC_FORMAT_MACROS -DDISABLE_NACL -DV8_TARGET_ARCH_ARM -DCHROMIUM_BUILD -DNDEBUG -DNVALGRIND -Iv8/src -MMD -
[06:19] <armin76> MF out/Release/obj.host/v8_nosnapshot/gen/libraries.o.d.tmp -c -o out/Release/obj.host/v8_nosnapshot/gen/libraries.o out/Release/obj/gen/libraries.cc
[06:19] <armin76> cc1plus: error: unrecognized command line option "-m32"
[06:19] <armin76> make: *** [out/Release/obj.host/v8_nosnapshot/gen/libraries.o] Error 1
[06:21] <armin76> ah well, you hit the same issue :)
[09:51]  * bizkut is away (i am away now)
[09:59]  * armin76 looks at lool 
[10:00] <armin76> fta: seen the armel build failure of crhomium?
[10:02] <shenki> armin76: looks like v8 hasn't been set up to build natively for arm yet
[10:02] <shenki> armin76: do you know if fta has a bug open for that?
[10:03] <armin76> shenki: no clue
[10:04] <shenki> you guys are the only ones that are attempting to build chromium natively; upstream does cross builds, and so do I
[10:04] <shenki> (i've been babysitting the arm build for the past 6 months or so)
[10:05] <armin76> i know, buts its fun ricing!
[10:05] <shenki> :D
[10:05] <shenki> how much RAM do the build machines ahve?
[10:09] <armin76> 512mb, i guess
[10:09] <armin76> no clue
[10:09]  * armin76 is not ubuntu dev, nor related to ubuntu at all
[10:09] <armin76> but they should be either marvell dove or imx515, which means 800mhz && 512mb afaik
[10:12] <shenki> nice. so it takes about a week to link? :)
[10:12] <armin76> takes 10 hours to do all
[10:17] <armin76> shenki: have you tried the crossbuilds?
[10:19] <shenki> armin76: yeah, i wrote the cross build infrastructure for arm. it takes about half an hour on my phenom-II 3ghz, with 4G of ram
[10:19] <armin76> shenki: but does it work? :P
[10:19] <shenki> s/wrote/helped write/
[10:19] <shenki> yeah, it does
[10:19] <armin76> fully?
[10:19] <armin76> have a binary i could test?
[10:19] <shenki> well, i don't build the tests
[10:20] <shenki> but yes, i have buildt and run binaries
[10:20] <shenki> i'll build you one now and upload it
[10:20] <armin76> thanks
[10:20] <shenki> what hardware do you have?
[10:21] <armin76> sheevaplug, efikamx and ssh access to marvell disco duo
[10:21] <shenki> i'm not familiar with the 2nd two. what architecture are they?
[10:21] <armin76> armv7a and armv5te
[10:22] <armin76> the latter has 3g of ram :)
[10:22] <shenki> !
[10:22] <shenki> want
[10:22] <armin76> ubuntu has plenty of them, ask asac :D
[10:23] <shenki> ah, but it's only armv5
[10:25]  * lool whistles
[10:25] <shenki> armin76: the chromium i build is for thumb2, is that okay?
[10:25] <armin76> shenki: guess so, will take a while to test it then, as the efika is a bit busy atm
[10:26] <shenki> hrm. i don't have a v5 rootfs, so it's a bit harder to build for that
[10:26] <armin76> don't worry
[10:27] <armin76> :D
[10:29] <shenki> armin76: what does the efika use for it's hdmi output?
[10:29] <armin76> and hdmi port :D
[10:29] <shenki> er, in terms of hardware. does it have a open driver?
[10:30] <armin76> nope
[10:30] <shenki> (i brought a openrd client and have been mega annoyed at not being able to use a modern kernel on it, due to no support for the video card)
[10:30] <armin76> does the beagleboard have open driver?
[10:31] <shenki> yeah
[10:31] <armin76> guess its the only one
[10:31] <armin76> afaik marvell dove has no open driver as of now
[10:31] <shenki> not for the 3d hardware, but it can display graphics no worries using the kernel driver. it's just been re-written too, presumably it's better
[10:31] <shenki> ok
[10:32] <shenki> that blows. silly embedded companies.
[10:33] <cwillu_at_work> armin76, recent dss2 work has made settings modes quite nice, although it's not quite xrandr yet.
[10:34] <shenki> cwillu_at_work: do you know if the dss2 stuff can allocate framebuffer memory dynamyicly (as in, when it sees how big the display it's driving is). or do we still need to provide it with the kernel boot args?
[10:34] <shenki> err, excuse the typos
[10:35] <cwillu_at_work> shenki, I don't know about going to bigger sizes than the initial framebuffer, no;  I've mostly been concerned with 1280x1024x16 myself
[10:36] <shenki> cwillu_at_work: ok
[10:36] <cwillu_at_work> it'd be easy enough to try though, although I don't have a spare board handy at the moment (my only board is tied up with some tests today)
[10:36] <shenki> yeah, i should just try it
[10:37] <armin76> shenki: i have sh board that has a siliconmotion gfx
[10:37] <armin76> the fun is that the x11 driver doesn't detect it :D
[10:38] <shenki> :/
[10:38] <shenki> someone should make some embedded gpu IP, and write an open driver for it. i imagine they would do quite well out of it
[10:52] <lool> armin76: The dove drivers are pretty open
[10:52] <lool> https://code.launchpad.net/~lool/+junk/marvell-libgfx http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-dove.git
[10:53] <armin76> lool: junk :D
[10:53] <armin76> shenki: ^
[10:55] <shenki> thanks
[10:57] <lool> armin76: Yeah, I hate that name; it's the name of a special folder where you can push any branch
[10:58] <lool> armin76: launchpad forces you to push to lp:$people/$project/$branch kind of trees
[10:58] <lool> e.g. lp:~ubuntu-core-dev/apt/ubuntu
[10:58] <lool> The special /+junk allows you to throw in any branch you like
[10:58] <lool> Without having to register a project first
[11:00] <shenki> armin76: ah, you're on gentoo? i wonder if the ubuntu builds will run on your system
[11:00] <armin76> shenki: who knows
[11:01] <lool> In theory they shold
[11:01] <lool> should
[11:11] <shenki> not really, ubuntu/debian names some libraries differently which throws the dynamic linker out
[11:13] <shenki> also you need to be running similar versions to the ones i linked against in my rootfs
[11:18] <shenki> armin76: http://jms.id.au/~shenki/chromium-arm-r35329.tar.bz2
[11:19] <armin76> shenki: got it, thanks
[11:19] <shenki> armin76: no worries. let me know how it goes
[12:28] <lool> shenki: Most libs have identical SONAMEs in Debian and Ubuntu; which ones did you have in mind?
[12:43] <shenki> lool: not sure, im not a gentoo user.  i was trying to convince a friend to use the google-built images and he had trouble
[12:55] <asac> shenki: armin76: yeah. seems to be an issue with "toolsets"
[12:56] <asac> like it sets -m32 if _toolset==host
[12:56] <asac> not sure where in gyp that toolset thing is done
[12:56] <asac> any idea?
[12:56] <armin76> grep :D
[12:56] <asac> armin76: haha
[12:56] <asac> already did that
[12:56] <asac> didnt find the trick
[12:57] <asac> i see where it sets -m32 if toolset==host
[12:57] <asac> but i dont see how the hell toolset = host
[12:57] <asac> _toolset=host
[12:57] <asac> actually
[12:57] <armin76> maybe its host = toolset *G*
[12:57] <asac> ho
[12:57] <asac> ho
[12:58] <asac> ho
[12:58] <armin76> merry christmas asac
[12:59]  * asac waits for shenki to tell me ;)
[12:59]  * asac kicks off a fresh build for a bug
[12:59] <asac> file
[13:00] <asac> armin76: http://code.google.com/p/chromium/issues/detail?id=31063 ... thats our snap with javascript bug ;)
[13:03] <armin76> :D
[13:04] <armin76> asac: sorry i forgot to run the backtrace, do you still want me to do it?
[13:04] <christoph_debian> hm maybe someone wants to update https://wiki.ubuntu.com/ARM ? it still tells arm5t ?
[13:04] <christoph_debian> don't like to ask around on IRC on multiple channels to find out my CPU is no longer supported
[13:05] <asac> armin76: give it a try. though its not meanng much until we have a snapshot biuld
[13:05] <asac> and thtahat has the same issue
[13:06] <asac> christoph_debian: feel free to update that page?
[13:06] <asac> ;)
[13:08] <asac> done
[13:08] <asac> hmm. not sure about karmic
[13:08] <armin76> karmic is armv6 you slacker
[13:09] <christoph_debian> asac: tells mit it's a ineditable page?
[13:09] <asac> christoph_debian: you need to log in ;)
[13:09] <asac> i updatred it now
[13:09] <asac> check if that is good enough for you
[13:10] <christoph_debian> I'd had put it into FAQ as well (the difference point tells it's v5 opposed to debian's v4) but it's quite vissible this way
[13:10] <christoph_debian> (login requires an account)
[13:12] <asac> ok let me edit that too
[13:12] <asac> done
[13:13] <asac> check it please
[13:13] <asac> (FAQ)
[13:13] <asac> shenki: ping me when back ;)
[13:13]  * asac makes some coffee
[13:31] <asac> shenki: armin76: http://code.google.com/p/chromium/issues/list?thanks=31274
[13:32] <asac> fta: ^
[13:33] <fta> asac, wrong link?
[13:33] <fta> crbug.com/31274 ?
[13:34] <fta> seems more like it
[13:34] <asac> hmm
[13:34] <asac> guess os
[13:37] <fta> triagged
[13:44] <asac> ok patched that stuff away ... lets see
[13:50] <asac> 14:49 < jdstrand> asac: netbook-launcher-efl accepted
[13:50] <asac> ole!
[14:03] <asac> NCommander: did you check whether kexec sitll broken on arm?
[14:08] <asac> fta: so triaging means its still left in unconfirmed state?
[14:08] <asac> it was confirmed by armin76 and me ;)
[14:12] <fta> asac, well, i usually semi-triage stuff, i won't assign a milestone as i'm not release manager there
[14:13] <fta> just moved it to untriaged, meaning confirmed but not reviewed for priority & assignment
[14:15] <asac> where do i see "untriaged"?
[14:15] <asac> i always say "unconfirmed" ;)
[14:15] <asac> see
[14:15] <fta> status
[14:15] <asac> what does available mean?
[14:16] <fta> you can't set it yourself, you have to be bugcontrol
[14:16] <fta> available is fully triagged, but not assigned
[14:16] <asac> ah
[14:16] <asac> felt like "fixed" ;)
[14:16] <asac> which would have been odd
[14:17] <asac> fta: do you see where _toolset is defined?
[14:18] <fta> asac, http://www.sofaraway.org/ubuntu/tmp/chromium-status.png
[14:18] <asac> its odd as i see toolset without _ being tested elsewhere
[14:18] <asac> and i see _toolset nowhere being set
[14:18] <asac> neither gyp code, nor chromium
[14:19] <asac> are there .py extensions to .gyp in the chromium tree?
[14:19] <asac> i only grepped in .gyp there
[14:19] <fta> grep gyp and gypi
[14:19] <asac> hmm. i think i also tried that
[14:19] <asac> let me check
[14:19] <fta> i need to run, be back later
[14:20] <asac> there are only tests
[14:20] <asac> no sets
[14:22] <asac> hah
[14:22] <asac> found it
[14:22] <asac> LoadAutomaticVariablesFromDict
[14:22] <asac> http://paste.ubuntu.com/348585/
[14:31] <armin76> quick
[14:34] <asac> still ;)
[14:34] <asac> no clue how this whole thing works
[14:34] <asac> e.g. is that injected from outside ... detected during build time? etc.
[14:57] <asac> hmm ... now the build failed with the same "pure virtual function called"
[16:17] <armin76> asac: what did you do?
[16:18] <asac> armin76: i dropped the -m32 flags hackishly
[16:20] <armin76> hah
[16:26] <asac> armin76: http://paste.ubuntu.com/348631/
[16:48] <armin76> asac: which gcc are you using?
[16:51] <asac> armin76: tried both: gcc-4.4 and gcc-4.3
[16:51] <asac> gcc-4.4.real (Ubuntu 4.4.1-4ubuntu8) 4.4.1
[16:51] <asac> Copyright (C) 2009 Free Software Foundation, Inc.
[16:51] <asac> This is free software; see the source for copying conditions.  There is NO
[16:51] <asac> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[16:51] <asac> hmm
[16:51] <asac> though i didnt build all with g++-4.3 yet
[16:51] <asac> maybe i should try
[16:51] <asac> i now disabled arm_thumb=0 alltogether
[16:51] <asac> seems the v8 code generation has special casing
[16:52] <asac> so could be that the combination armv7=0 arm_thumb=1 isnt good
[16:53] <asac> ok kicking a new build with AVOID_GCC44
[16:57] <asac> armin76: http://pastebin.com/f73b8edfb
[16:57] <asac> thats the hackish patch to continue
[16:57] <asac> you didnt get the virutal func issue before, so maybe it just works for you with that
[19:22] <armin76> asac:   export LD_LIBRARY_PATH=/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/lib.host:/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/lib.target:$LD_LIBRARY_PATH; cd v8/tools/gyp; mkdir -p /var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/obj.target/geni; "/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/mksnapshot" "/var/tmp/portage/www-client
[19:22] <armin76> /chromium-9999/work/chromium-9999/out/Release/obj.target/geni/snapshot.cc"
[19:22] <armin76> /bin/sh: line 1: 14154 Segmentation fault      "/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/mksnapshot" "/var/tmp/portage/www-client/chromium-9999/work/chromium-9999/out/Release/obj.target/geni/snapshot.cc"
[19:22] <armin76> make: *** [out/Release/obj.target/geni/snapshot.cc] Error 139
[19:39] <fta> armin76, looks familiar, could you get a backtrace?
[21:07]  * bizkut is away (i am away now)
[21:15] <asac> armin76: so its still building with gcc 4.3
[21:15] <asac> nice
[21:15] <asac> armin76: do you get a reasonable backtrace  for that seg?
[21:16] <asac> the sigill is just rubbish. maybe thats a better hint to see whats going on
[21:16] <lool> asac, ogra_: http://paste.ubuntu.com/348756/
[21:16] <lool> Will send to qemu-devel@ shortly
[21:19] <asac> nice
[21:20] <lool> I had also noted that I should fix qemu to sigill on instructions not in the emulated CPU, but actually it does
[21:20] <lool> qemu-arm takes a -cpu arg, just like the system one
[21:20] <lool> It's just the man page which sucks
[21:52] <asac> cool ;)
[21:52] <asac> armin76: mine is still spinning ;)
[21:52] <asac> something must be wrong :)
[22:21] <armin76> lool: funny away msg! :P
[22:21] <armin76> fta: asac: will check tomm, i'm tired atm
[22:27]  * lool is away (not reading armin76's temptations)