/srv/irclogs.ubuntu.com/2009/11/29/#ubuntu-arm.txt

=== asac_ is now known as asac
armin76asac: did it bumb? :D11:56
asacarmin76: the build failed ... but but but ... i dont see any error ;)13:42
asacworst case i would say ;)13:43
asaclet me try to get the log somewhere13:43
* lool wins \o13:43
loolasac: Was a date set to move armel to archive.u.c?13:45
asac http://people.canonical.com/~asac/tmp/chromium-browser_4.0.260.0~svn20091128r33239-0ubuntu1~ucd1_armel.build.bak.bz213:47
asaclool: ^^13:47
asacno error ;)13:47
asacbut still build failed13:47
asaci ran the last command you can se there ... linked fine ;)13:47
asacnot sure whats going on13:47
asaci guess OOM ;)13:47
asaclool: not sure that it was discussed. was that prediscussed/should i add that as a lucid goal?13:50
loolasac: scons: *** [/home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/obj/icu/icudata/linux/icudt42l_dat.o] Error 113:50
loolas -o /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/obj/icu/icudata/linux/icudt42l_dat.o /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/third_party/icu/linux/icudt42l_dat.s13:50
lool/home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/third_party/icu/linux/icudt42l_dat.s: Assembler messages:13:50
lool/home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/third_party/icu/linux/icudt42l_dat.s:2: Error: junk at end of line, first unrecognized character is `,'13:50
lool/home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/third_party/icu/linux/icudt42l_dat.s:5: Error: unrecognized symbol type ""13:51
loolasac: Doesn't look like oom to me13:51
asacoh13:51
asacdarn chromium build system13:52
asac--keep-going13:52
asacwhat a bad invention ;)13:52
asaci looked from the back ;)13:52
lool--keep-going is called from the rules13:52
asacyes13:52
asacthats the bad thing13:52
loolSo you could trash it, it's not scons' default13:52
asaci dont know why fta has it13:52
asacsure13:52
asacalready done13:52
loolWell if you know it's there, I find it helpful13:52
asacalso did it before, just took latest snapshot and forgot to remove that13:52
asacwhy would you want to keep going? because scons is too slow to do quick incremental builds?13:53
loolThe nice thing is that you know there is only this one error from everything which could be build in this pass; perhaps other errors will popup later, but it tested a good part of the build already13:53
loolYou might want to "fire the build and forget" and then look back at all errors, especially on random arches13:54
lool(on buildds)13:54
loolIt's a compromise because it also wastes a lot of machine time if things go wrong every time; if you do fix build failures, it saves machine time though13:54
loolAnyway, matter of taste13:54
asacright13:55
asacjocote:/tmp/icudt42l_dat.s13:55
asaclool: ^13:55
* asac gets coffee ;)13:56
loolasac: I'd disable stack protection for now; it seems to be broken in the toolchain here; would be nice to keep the test case though13:58
armin76asac: who won? :)13:58
loolasac: Just pass -fno-stack-protector13:58
loolin CFLAGS13:58
loolarmin76: You're a gentoo guy right?13:59
giorgio__Hi13:59
armin76lool: yep13:59
loolarmin76: I find http://www.gentoo.org/proj/en/hardened/gnu-stack.xml really nice14:00
giorgio__to build my ubuntu-arm image for beagle board, should i have ubuntu on my development PC (i.e. to be compatible with rootstock) or i can use kubuntu without problems ?14:00
loolarmin76: What do you work on in gentoo?  arm porting?14:01
giorgio__i would save time to install ubuntu14:01
armin76lool: we're nice ppl :P14:01
loolgiorgio__: kubuntu should be just fine14:01
giorgio__i'm asking 'cause i cannot fetch rootstock from apt-cache search14:01
armin76lool: http://armin762.wordpress.com/about/14:01
loolgiorgio__: kubuntu and ubuntu are built from the same underlying packages, just a different selection / default config, so worst case you have to install a couple more packages14:01
loolgiorgio__: Which release are you on?14:01
giorgio__i installed an old one, and the let it upgrade itself, it should be kubuntu 9.0414:02
giorgio__maybe i have tu follow the instruction for Jaunty ubuntu ?14:02
loolarmin76: good to know, thanks14:03
loolgiorgio__: rootstock is shipped in ubuntu/kubuntu since karmic14:04
loolgiorgio__: So either upgrade to karmic (you'll have to at some point anyway   ;-) or add the rootstock jaunty PPA to your config14:05
loolgiorgio__: Also note that rootstock is in universe, so this needs to be enabled (isn't by default)14:05
giorgio__ok thanks, i'm following the instructions for jaunty, i think should not be different14:07
giorgio__hope difficult either :D14:07
loolasac: I can't figure why "," would be an invalid char; it seems fine from the example in http://www.gentoo.org/proj/en/hardened/gnu-stack.xml14:07
armin76icu sucks14:10
armin764.2.1 fails for me on arm, i think it was assembler related thing as well14:10
armin76haven't had time to look at it14:10
armin76but on debian it built fine...14:10
asaclool: using @progbits helps14:18
asacerr14:18
asac%progbits ;)14:18
asaclike on the gnu-stack.xml14:18
asachttp://paste.ubuntu.com/331089/14:19
asacdoes that make sense ;)?14:19
asac%object i did too ;)14:19
loolasac: Yeah I spotted the @ versus %, but other examples say @; not sure what it means14:21
asaclool: i changed %progbits and %object ;) ... whats the difference ;)14:21
asacwow ... really huge .s file ;)14:24
asac6M gzipped ;)14:24
asaclool: so @ works on x86 ... but % works too14:25
asacreadelf -S looks identical at least14:26
asaclool: where is a @ example?14:27
asachttps://svn.pardus.org.tr/pardus/2009/stable/system/devel/gcc/files/note-gnu-stack.dpatch14:28
asacseems %progbits is used for arm stuff14:28
asaceverywhere else its @objcet14:28
asacerr @progbits14:28
asactoo bad i dont have lucid chroot14:28
asaclool: i assume you have no lucid toolchain on your board and you could check whether thtas still needed?14:30
armin76asac: i won!14:33
armin76now you owe me an armv7 board14:33
asacarmin76: we will see ;)14:34
asacarmin76: i am still convinced your talent would be better invested in the ubuntu project ;)14:34
asacnow the build is at linking stage14:36
asaci guess that will consume all damn mem and swap together ;)14:36
asac"Note on targets where the @ character is the start of a comment (eg ARM) then another character is used instead. For example the ARM port uses the % character."14:47
asaclool: ^14:47
asachttp://sourceware.org/binutils/docs-2.20/as/Section.html#Section14:47
asacok that explains it ... guess we need and #if defined...14:49
asacbut which one ;)14:49
loolasac: I dont have a lucid host yet15:13
loolasac: What is that .s generated from?15:14
asacgood question ;)15:15
asaclet me check15:15
loolFrom ./build-tree/src/third_party/icu/source/data/in/icudt42l.dat15:17
asaci dont see where it gets generated15:18
loolIt might be pregenerated in the tree15:18
asacright thats what i think15:19
loolIt's really slow to unpack lzma though15:19
lool-rw-r--r-- fta/fta    25347229 2009-11-26 16:02 src/third_party/icu/linux/icudt42l_dat.s15:19
asacso we either need to hope that % really works everywhere15:19
loolIt is pregenerated15:19
armin76chromium's build system sucks :P15:19
asacor we have to ship two different files ;)15:19
asac% works at least here on x8615:19
asacfeels ugly though if gnu docs say @ ;)15:19
loolasac: It might mean something else on x86?15:20
asaclool: the readelf looked identical at least ;)15:21
lool         # These are hand-generated, but will do for now.  The linux15:21
lool         # version is an identical copy of the (mac) icudt42l_dat.s file,15:21
lool         # modulo removal of the .private_extern and .const directives and15:21
lool         # with no leading underscore on the icudt42_dat symbol.15:21
lool        'linux/icudt42l_dat.s',15:21
asacright.... but _how_ are they hand generated ;)15:21
lool    - {mac,linux}/icudt42l_dat.s : Built on Mac and Linux with all the15:22
lool      patches above applied and checked in.15:22
lool    - source/data/in/icudt42l.dat : Built on Linux with all the patches15:22
lool      above applied,15:22
lool11. Pre-built data libraries are checked in.15:22
asaci see that section15:22
loolbuild-tree/src/third_party/icu/README.google15:22
loolGiven that it's to put this in a symbol in a .o, I wonder whether they could generate a C file instead15:23
asacyes. but you have to wrap each line with asm("... right?15:24
loolI think it's just data; they could export a const array15:25
loolThe declaration says it's not executable anyway15:26
loolSo something like unsigned long data[] = {0x...};15:26
asachmm15:27
lool+ static15:27
loolIt's in section .rodata, so clearly const15:27
asacyep15:27
lool.align 8 => can probably be achieved with __attribute__15:27
loolNot sure what .type icudt42_dat,%object means15:27
asaci asked on the #chromium channel now ... lets see if anyone answers15:28
asachttp://sourceware.org/binutils/docs-2.20/as/Type.html#Type15:28
lool"Mark the symbol as being a data object. "15:28
loolRight just landed on that page as well15:29
asachmm so STT_OBJECT?15:29
loolDoes this exist in C?15:29
loolI'm not even sure this stuff is needed15:29
asacok STT_OBJECT works15:30
loolin C?15:31
asacno in .s15:32
asac        .type icudt42_dat STT_OBJECT15:32
asacrather than ,@object15:32
asacdoc says thats the gnu arch independent way15:33
loolWell yes, that's the same thing15:33
asacthat reduces the problem to the progbits ;)15:33
loolI was proposing to move this whole .s stuff to .c to aovid the porting issue15:33
asacwhich doesnt really help :)15:33
asacright15:33
asaci understood15:33
loolOh the object part was rejected as well?15:33
asacyes15:33
asac@ is a comment on arm asm15:34
loolOk didn't see that far15:34
loolRight15:34
asacNote on targets where the @ character is the start of a comment (eg ARM) then another character is used instead. For example the ARM port uses the % character.15:34
asachttp://sourceware.org/binutils/docs-2.20/as/Section.html#Section15:34
asachell ... i want a portable for that too ;)15:34
loolYup, read that too; just didn't spot use of @ in object15:34
asacor know how the .s is generated so we can create a .c15:34
asacah ok15:34
loolWell to me it seems the .s is just the bytes from the .dat15:35
asac#chromium channel folks are laggers ... noone replying sundays as it seems ;)15:35
loolhaha15:35
asacyes. but there must be  ascript or something ;)15:35
asacso we want to use static unsigned long icudt42_dat[] { .... } ?15:36
asacfeels like we could even postprocess that from the .s file ;)15:37
asacecho "const unsigned long icudt42_dat[] = {" > out.c; grep ^\.long icudt42l_dat.s | sed -e 's/\.long//' | sed -e 's/$/,/' >> out.c; echo '};' >> out.c15:46
asacmight complain about final , ;)15:47
asaclool: isnt the alignment automatically done by gcc?15:49
loolasac: Only on size long15:49
asachmm15:49
loolIt might be more, but how do you know?15:49
asacso __attribute__ ((aligned (8))); ?15:51
loolYup15:51
asacecho "const unsigned long icudt42_dat[] = {" > out.c; grep ^\.long icudt42l_dat.s | sed -e 's/\.long//' | sed -e 's/$/,/' >> out.c; echo '} __attribute__ ((aligned (8)));' >> out.c15:52
loolI checked build-tree/src/third_party/icu/linux/icudt42l_dat.s, it starts with the same bytes as build-tree/src/third_party/icu/source/data/in/icudt42l.dat15:52
asachmm15:52
asacok so we could write the full binary generator15:52
asacisnt there such a tool already ;)15:52
asacmust be somewhere15:52
loolasac: FYI, the conversion is completely unportable like this15:52
loolIt uses long despite the fact that it's represented differently on little endian and big endian arches15:52
loolI think we just want some uint8_ts15:53
asacmaybe the code consuming this does the endianess shuffeling?15:53
asacdo we know?15:54
loolI have my doubts15:54
asacwhy is ICU such a mess ;)15:55
giorgio__do you know anything about touch screen issues with the beagleboard ?15:55
loolI did a grep -rl icudt42_dat build-tree/src/* but couldn't find where the symbol was used exactly15:55
asacheh15:55
loolasac: and the end of the file is also the same15:55
asacright15:55
asacthats expected (now)15:55
asacso the gcc on the out.c runs for 5 minutes already ;)15:56
asacok to be fair chromium is linking in the background ;)15:56
lool10515 asac      20   0  494m 140m   84 R  1.3 29.8   1:56.70 cc115:57
asacyep ;)15:58
asacthats the out.c one15:58
asacas was much faster ;)15:58
loolI'm just scared with the memory use15:58
asacyeah. probably HUGE array gets parsed first15:58
asaclet me abort that for now15:58
asacgive some air to breath to ld15:59
asac;)15:59
loolld is also hungry15:59
lool 8683 asac      20   0 1245m 352m   76 D  3.2 74.7   5:59.52 ld15:59
asacright15:59
asacbut thats expected15:59
asacchromium takes like 3G16:00
loolwow16:00
asacwe only have 512m :(16:00
asacfor linking16:00
asacit links everything static16:00
asacand does that for 1000 binaries or so ;)16:00
asacall tests etc.16:00
asaclool: did you succeed with your full/dynamic arm chroot thing?16:01
loolI stopped at UDS16:01
asackk16:01
loolI need to finish this16:01
loolI clearly didn't manage to avoid binfmt though16:01
loolIt might be possible with some awful hacks16:02
ftamost chromium devs use gold instead of regular ld, but i don't know for arm16:08
asacdo you know where this icu blob is actually used ;)?16:08
asacicudt42_dat16:08
ftaAssembling /build/buildd/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/obj/icu/icudata/linux/icudt42l_dat.o16:09
ftaCreating library /build/buildd/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/lib/libicuuc.a16:09
asacyes16:09
loolasac: No, as I said above I grepped for it and couldn't find it16:09
asacright thats why i asked fta ;)16:09
asac(sorry for missing nick)16:09
loolI found it referenced in other .a files, but I didn't see where the symbol was used16:09
loolOh sorry16:09
asaclool: referenced in other .a files?16:09
asacwhich one?16:10
loolSorry off buffer16:10
loolgrepping again16:10
asac:)16:10
giorgio__wich is the newest kernel version and where i can get the link to pass to rootstack ?16:12
ftahttp://code.google.com/p/chromium/issues/detail?id=2236916:13
loolgiorgio__: We dont support beagleboard kernels sadly16:13
loolbuild-tree/src/sconsbuild/Release/lib/libicuuc.a16:14
loolbuild-tree/src/sconsbuild/Release/lib/libicudata.a16:14
loolasac: ^16:14
loolit continues16:14
asacnm on those?nm build-tree/src/sconsbuild/Release/lib/libicuuc.a | grep icu.*_dat U icudt42_dat16:15
giorgio__lool: i found it, simply navigate in the rcn-ee.net website16:15
giorgio__tnx anyway16:15
asacnm ./build-tree/src/sconsbuild/Release/lib/libicudata.a16:15
asacicudt42l_dat.o:16:15
asac00000000 R icudt42_dat16:15
loolbuild-tree/src/sconsbuild/Release/obj/icu/icuuc/source/common/udata.o16:16
loolbuild-tree/src/sconsbuild/Release/obj/icu/icudata/linux/icudt42l_dat.o16:16
loolOh right it's mentionned in some tests as well16:17
asacbuild-tree/src/third_party/icu/source/common/umapfile.c:#       define U_ICUDATA_ENTRY_NAME "icudt" U_ICU_VERSION_SHORT U_LIB_SUFFIX_C_NAME_STRING "_dat"16:18
asaclool: ^16:19
asacso U_ICUDATA_ENTRY_NAME16:19
armin76lool: why don't you support beagleboard?16:19
asacloaded question i guess16:20
asacwe provide rootstock ;)16:20
ftaasac, lool: which version are you using, in r30145, there's a fix for icu on arm, but 1 month old now16:20
armin76asac: did you saw the link fta posted?16:20
asacfta: I use latest daily16:20
asacfta: link to that commit?16:20
ftahmm16:20
armin76asac: but thats not commited?16:21
asacmaybe icu snapshot wasnt bumped to latest?16:21
armin76oh, it is16:21
armin76well, i don't understand google code :P16:21
ftahere is the patch http://codereview.chromium.org/33803116:21
asacis icu a copy? not a on-demand checkout?16:21
asacok16:21
asacheh16:21
asacyes16:21
asacthats the fix16:22
asacthough .type icudt42_dat STT_OBJECT is "better" ;)16:22
ftai know, but it's strange you still see it though16:22
asacfta: why isnt that in daily?16:22
asacguess it wasnt committed?16:22
ftait was, as i said, it's in r3014516:23
asacwhen was it backed out ;)?16:23
asacwhen they merged icu?16:23
asaccan you confirm that its not in anymore? or is our tarball bogus?16:24
ftachecking16:26
loolasac: http://paste.ubuntu.com/331166/16:26
asacyeah16:27
asac17:18 < asac> build-tree/src/third_party/icu/source/common/umapfile.c:#       define U_ICUDATA_ENTRY_NAME "icudt" U_ICU_VERSION_SHORT U_LIB_SUFFIX_C_NAME_STRING "_dat"16:27
asac17:19 < asac> lool: ^16:27
asacso grepping for U_ICUDATA_ENTRY_NAME gives the usesin code16:27
asacnot sure if we should check if that deals with endianes properly there16:27
ftachromium pulls /trunk/deps/third_party/icu42@32651 so it's in. are you sure you're patching the same file?16:31
asacso this was committed to icu tree?16:31
asacwhere i sthe tree?16:31
asac(svn)16:31
ftahttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/16:32
asacthx16:32
loolasac: Ah cool, that's what I would have grepped next, but I feared being overwhelmed with results16:33
asachttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/linux/icudt42l_dat.s?revision=32640&view=markup16:35
asacfta: ^^16:35
asacits clearly not on trunk anymore16:35
asaci dont even see any commit backing that out ;)16:36
asachttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/linux/icudt42l_dat.s?r1=26784&view=log16:36
asachow can i get longer log for that?16:36
asacoh maybe they added it to 38?16:36
ftaviewvc is crap16:36
asacno ... its not there either :/16:36
asachttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu38/linux/icudt38l_dat.s?view=log16:36
asachttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu38/linux/icudt38l_dat.s?revision=2473016:36
asacits odd if i look at the diff to previous of the ARM portable commit16:38
asacit _adds_ the @ stuff16:39
asachttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/linux/icudt42l_dat.s?r1=25651&r2=2678416:39
asacoh ;)16:39
asacits on the right16:39
asacdidnt even see anything of that on my screen :)16:39
asacyeah. so this regressed in commit http://src.chromium.org/viewvc/chrome?view=rev&revision=2972816:39
armin76reverted :)16:40
loolasac: http://paste.ubuntu.com/331180/16:42
loolasac: Change "L>*" to "L*" to use native encoding; "<" is LE, ">" is BE16:42
lool(nothing is whatever the host runs == native)16:43
loolAnd tweak $chunk and sprintf as you please16:43
armin76lool: asac was compiling with -j816:43
* armin76 runs16:43
asac?16:44
armin76asac: j/k16:44
loolasac: if you talk to upstream, would love if you made them generate a .s or .c at build time; it's one less large and weird sourcefile and more maintainable for us in such cases16:44
asacack16:44
asacthats what we should be aiming for i guess16:45
ftaasac, 32640 did it16:47
ftacrbug.com/2040616:48
loollove that URL scheme16:49
loolfta, asac: So it's pretty clear the fact that the generation happens manually participated in this issue.... :-(16:50
loolanyway /me runs &16:50
asacenjoy16:50
ftahttp://src.chromium.org/viewvc/chrome/trunk/deps/third_party/icu42/README.google   look at 11.16:53
ftaasac, i will reopen the bug16:57
asacyes... already read16:57
fta(i'm bugcontrol there)16:57
asacfta: can you suggest to generate those on the fly?16:58
ftait seems difficult based on all the changes mentioned in the readme17:00
asacfrom what i understand the changes are done to the .dat file17:00
asacso that one would be the base for mac/linux at least17:00
asacwhich bug will you open=17:03
asacthere were two ;)17:03
asachow much faster would chromium finish if built without tests? ;)17:04
asac:-P17:04
ftaI build it in 20 minutes here ;)17:04
asacg++ -o /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/ui_tests17:06
ftai reopened crbug.com/2040617:06
asacwithout comment?17:07
asachmm that bug is a different one17:07
asacnot the ARM regression bug17:07
ftaoops, crbug.com/2236917:07
ftabad paste buffer17:07
asachttp://code.google.com/p/chromium/issues/detail?id=2236917:07
ftaasac, anything else broken on arm?17:25
asaccant tell ;)17:25
asacbuild is slow17:25
asaclinking17:25
asacatm17:25
asacfta: we should add armv7=1 to GYP_DEFINES17:26
asacif we are on armv7 i guess17:26
asacat least i added it here ;)17:26
ftacould you please paste a dpkg-architecture?17:27
asachttp://paste.ubuntu.com/331205/17:27
asacdoesnt show if we are on v717:27
ftauname -m?17:28
asac$ uname -m17:28
asacarmv7l17:28
ftabetter17:28
ftado you have other flavors you want to support?17:28
asaci am not sure we want to not use the uname -m ... rather something that figures if the toolchain defaults to v717:28
asacfta: i think it would be nice if it also can be compiled on armv7 machines for hardy17:29
asacthats why we need to use toolchain or CFLAAGS or something to determine that17:29
asacfta: i think we want to use that for lucid and later17:40
asacfor now17:40
asacfta: tests are running ;)18:50
asac## list of FAILED tests:18:50
asac[  FAILED  ] ConditionVariableTest.FLAKY_MultiThreadConsumerTest (796 ms)18:50
asac[WARNING] /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/testing/gtest/src/gtest-death-test.cc:741:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads.18:51
asacTimeout: aborting command ``./base_unittests'' with signal 918:52
asacKilled18:52
asacquite a lot tests work though18:52
asacnice18:52
asacchromium-browser .deb seems to be done on jocote ;)20:55
asacfta: package is building -dbg .deb still ... is it normal that i see a test_shell_test process running still?20:56
asacbaseunit_tests too afaict20:56
asac17863 asac      20   0 77348    8    4 R 33.0  0.0  66:33.30 base_unittests20:56
asac22152 asac      20   0 47516    8    4 R 33.0  0.0  22:27.81 test_shell_test20:56
asac23507 asac      20   0  372m 368m   60 R 33.0 78.2  12:00.53 lzma20:57
ftanope, should have been killed by timeout21:02
asackk21:02
ftai use a timeout of 600 sec, it's usually enough to let each test run. the idea is just to prevent the build from being blocked on network accesses.21:04
ftaby default, the builder kills builds that didn't produce outputs for 4 hours, my stuff makes that 10 minutes minus the running time21:06
ftaso it seems timeout is broken on arm21:06
ftacould you check in the logs how base_unittests & test_shell_test ended up?21:07
ftaasac, ^^21:07
asacfta: build is still running ;) ... but let me look21:07
asacfta: http://paste.ubuntu.com/331304/21:09
ftahm, fork()21:11
ftai should kill those too21:11
ftai guess the ppid is gone, right?21:12
asac;)21:12
asacits defunct21:12
ftayep, that's expected21:12
asacasac@jocote:~$ ps -eaf | grep base21:12
asacasac     17600     1  0 18:47 ?        00:00:24 /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/base_unittests21:12
asacasac     17848 17600  0 18:48 ?        00:00:00 [base_unittests] <defunct>21:12
asacasac     17863 17600 49 18:48 ?        01:11:33 /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/base_unittests21:12
asacasac     25011 24437  0 21:12 pts/1    00:00:00 grep base21:12
asacso can i kill them without risking the packaging stop  ;)21:12
asac?21:12
ftayes21:12
asacthose dead tests consume 60% of CPU21:12
ftalol21:12
asacasac     22152     1 34 19:52 ?        00:27:57 /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/sconsbuild/Release/test_shell_tests21:13
asacthat is still running too21:13
asacguess same boat?21:13
ftaif the ppid is defunct, yes21:14
asacgreat ... funally lzma gets 70% of CPU ;)21:14
asacshould speed this up by factor 3 ;)21:14
asacppid was 1 ;)21:14
asac23507 asac      20   0  372m 364m   56 R 96.4 77.2  18:14.76 lzma21:15
asacyay21:15
asacfull speed21:15
asac-dbg21:15
asac ;)21:15
ftacould you pastebin your /proc/cpuinfo?21:16
asachttp://paste.ubuntu.com/33131021:17
ftafunny, it looks totally different from the usual format21:18
asacdifferent arch ;)21:18
asacno MhZ ;)21:18
ftai mean, the linux kernel usually spits something similar, same keys, different values21:19
asacfta: sparc: http://paste.ubuntu.com/331313/21:20
ftaoh21:21
asacfta: ppc http://paste.ubuntu.com/331314/21:21
asacso not really much in common ;)21:22
asachmm ... do we really need lzma ;) ... someone said lzma was awefully unoptimized on arm21:23
asaci see what that means atm ;)21:23
ftai can disable it easily for arm, i have a knob21:25
ftayou will just have 30% to 50% bigger debs21:25
ftabut with thumb, you can produce smaller binaries, so maybe that's ~21:25
asacyeah.21:26
asacfta: did you commit the regressoin unpatching yet? ... also the lucid == armv7 would be great so i can copy the sources to some native ppa for lucid/karmic tomorrow?21:26
ftaregressoin unpatching? you mean icu?21:26
asacyes.21:27
asacs/@/%/21:27
ftai didn't, i will kick upstream to have relanded asap21:27
fta+it21:27
asackk21:28
asaci think the karmic debs should be good enough to get someone trying to run those bits21:28
asacto get a first idea about how broken it is ;)21:28
asacbut you could add the lsb_release -c == lucid -> armv7=1 thing21:29
asacthats definitly wanted21:29
* asac can do that too21:29
ftayou mean, armv7 without even checking it's a v7 capable box?21:30
ftaWANT_TESTS = 0 too? (that's sad)21:32
asacfor 9.10 and above we dont support anything below v521:32
asacerr v721:32
asacyou could do a double check21:32
asacif armv7l or better and if lucid or newer -> do it21:32
asacso if someone ports lucid to armv6 or something it would still build21:32
asaci think we can keep tests on21:33
asacthey didnt take that much time after all ;)21:33
asacjust a few hours ;)21:33
asacmaybe ensure that its easy to unset that by env21:33
asac;)21:33
asacbut not really important21:33
asacalso a variable for KEEP_GOING=0 ;)21:34
asacmaybe just remember to kill those processes looping if the tests fail ;)21:34
asac: chromium-browser-inspector: image-file-in-usr-lib usr/lib/chromium-browser/resources/inspector/Images/warningsErrors.png21:38
asacW: chromium-browser-inspector: image-file-in-usr-lib usr/lib/chromium-browser/resources/inspector/Images/whiteConnectorPoint.png21:39
asacE: chromium-browser-inspector: copyright-should-refer-to-common-license-file-for-lgpl21:39
asacE: chromium-browser-inspector: lzma-deb-archive21:39
asacE: chromium-browser-l10n: copyright-should-refer-to-common-license-file-for-lgpl21:39
asacE: chromium-browser-l10n: lzma-deb-archive21:39
asacwe are close :)21:39
ftais it ok if i target the armv7 for ubuntu+1 instead of hardcoding lucid? i mean, lsb_release -ds matching either unstable or development to cover both debian & ubuntu21:39
asaci am not sure about the target arch of debian21:40
asacbut if you also check for target CPU then probably yet21:40
asacyes21:40
ftait will match sid and lucid21:40
asac(not sure what to test so we can still cross-compile )21:40
ftaof course, for arm(el) only21:40
asacfta: i know. but i odnt know what target sid has ;)21:40
asaci wouldnt necessarily say that they stop supporting armv521:41
asacwould have to check with whowever has a say on that in debian ;)21:41
asaclool: ?21:41
asacwho is that?21:41
asacBUILD FINISHED ;)21:42
asac\o/21:42
asaccheers21:42
* asac gets a drunk21:42
asacdrink ;)21:42
ftalol21:42
ftadoes it run?21:43
asaci have no local machine21:43
asaclool: wanna grab the debs from jocote and try? ;)21:43
asacits karmic build21:43
asacJamieBennett: ogra: NCommand`: ^^21:44
asacGrueMaster: ^^21:44
asac;)21:44
asacls ~asac/*.deb21:44
asacxforwarding seems to be not enabled there21:46
asachmm. maybe because it goes thorugh a ssh proxy? not sure21:46
asaclets hope for one of the above to test it ;)21:46
asacfta: arent there tests against xvfb ?21:46
ftayes, they are21:47
asace.g. couldnt i check if some test worked to see if chances are high that it works?21:47
asacfta: which test would i look for?21:47
ftathose are unittests, so not a guaranty that the whole thing runs :(21:48
asacwell21:48
ftatest_shell would be nice, but you still need a display21:48
asac[19742:19742:1129/193121:3402522844231:ERROR:/home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/base/shared_memory_posix.cc(192)] Creating shared memory in /dev/shm/com.google.chrome.shmem.unit_tests-19742 failed: Permission denied21:48
asaci see a bunch of those21:48
asacfeels like that could be a buildd setup problem21:49
asacfta: http://people.canonical.com/~asac/tmp/chromium-browser_4.0.260.0~svn20091128r33239-0ubuntu1~ucd1_armel.build.gz21:50
asacthtas the full log (incremental though)21:50
asacok seems /dev/shm has not right permissions in the chroot21:51
asacs -la /dev/shm/21:51
asactotal 821:51
asacdrwxr-xr-x 2 root root 4096 Sep  9 18:48 .21:51
asacbut outside of chroot its fine21:52
asacwill check with lamont21:52
ftayeah, 550 lines of d/rules file21:56
ftacrazy thing to build21:56
armin76asac: debian hasn't dropped i486 for i686, no point they are dropping armv521:58
asacwe havent dropped i486 either21:58
asac:-P21:59
armin76asac: are you still a debian dev?21:59
asacin my non-existing spare time ... yes ;)22:00
armin76asac: ok, another point: ubuntu doesn't support any publicly-available board, debian does22:01
asaci know22:01
armin76and they don't support any armv722:01
armin76nor anything avobe v5, for that matter22:01
armin76err, above :P22:02
asacnot sure what point you are trying to make ;) ... the question here was if we wanted to enable armv7 for debian sid ;) ... which i said was probably not right22:02
asacso you confirmed that i guess ;)22:02
armin76in fact debian supports armv4t, which the untouch gcc code didn't support, for example :)22:03
asaci think we support armv5 ... just not the kernel ;) ... so no image22:03
asacdoes debian offer images for all kind of arm SoCs?22:04
armin76hrm...i have no clue22:04
armin76i know the installer supports them, but not sure how you get the installer22:04
asacright22:04
asacthats what i mean. in general we support everything (well until lucid where we now make use of modern stuff)22:05
armin76asac: we as in ubuntu or?22:05
asacjust have no images... because we dont have kernels for all the SoCs that are out there ;)22:05
asacyes22:05
armin76debian has the kernels, though22:05
asacarmin76: which ones?22:06
asachttp://www.debian.org/ports/arm/22:06
armin76yep22:07
armin76i find funny you ask me, you being a debian dev :P22:07
armin76marvell kirkwood is supported on squeeze iirc22:08
asaci am not really into arm that long ;)22:08
armin76also i believe they only support those devices that have kernel.org support22:09
armin76anyway, let's focus on topic22:11
armin76asac: you owe me an armv7 board :)22:11
asacnoted22:11
armin76danke22:11
suihkulokkidebian supports only mainline kernel boards due to resource constraints22:12
suihkulokkithen again, any vendor claiming to support boards that are not mainlined is lying to their customers22:13
suihkulokki..in a few upstream kernel releases, the customer will find out that _they_ are not getting any kernel upgrades..22:14

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!