**** BEGIN LOGGING AT Wed Dec 09 20:33:20 2009 Dec 09 21:30:04 is it now possible to compile my code for arm on lp? Dec 09 21:36:37 or should i squeeze everything out of my n800? Dec 09 21:52:39 playya_: squeeze Dec 09 21:52:46 :/ Dec 09 21:53:17 i should use the 2 GB card for /var/cache Dec 09 21:54:19 but i can upload it to my ppa? Dec 09 21:59:06 playya_: ppas dont build for arm Dec 09 21:59:13 and you can only upload sources there Dec 09 21:59:20 ok Dec 09 21:59:25 bye bye n800 Dec 09 21:59:30 hehe Dec 09 21:59:31 see you in the next decade Dec 09 22:00:06 afair there's a bug report for it Dec 09 22:00:22 and the arm machines are quite idle most of the time Dec 09 22:00:37 i just want to build the fso stuff :( Dec 09 22:01:54 playya_: they are usually busy Dec 09 22:02:02 and break regularly atm Dec 09 22:02:10 now is freeze time Dec 09 22:02:16 thats why they are (luckily) idle Dec 09 22:02:24 just saw the load on a info page Dec 09 22:02:35 https://edge.launchpad.net/builders Dec 09 22:02:36 maybe that was on the end of a release cycle Dec 09 22:03:16 s/on/at/ Dec 09 22:52:43 asac, still there? Dec 09 23:00:46 fta: yes Dec 09 23:00:56 bb in 5 min Dec 09 23:01:35 asac, want me to bring the chromium/codec dev here? so it's faster and i don't act as a relay Dec 09 23:03:15 fta: why not ;) depends when he can make it though Dec 09 23:04:29 http://pastebin.com/f65476f12 Dec 09 23:04:43 that was the patch ... the other was about arm + fPIC afair Dec 09 23:05:11 hold on, asking Dec 09 23:11:04 fta: when basetest is running are all the debs already produced? Dec 09 23:11:28 nope, debs are created at the end Dec 09 23:11:45 oh no :( Dec 09 23:11:55 this thing from yesterday is still running Dec 09 23:12:02 lol Dec 09 23:12:17 thats not acceptable ;) Dec 09 23:12:34 maybe we should skip the test on arm then Dec 09 23:12:34 maybe i should really try qemu ;) Dec 09 23:12:38 testS Dec 09 23:12:46 i think so ... for now Dec 09 23:13:49 ipc_tests now Dec 09 23:14:26 awong, welcome! Dec 09 23:14:33 hello! Dec 09 23:15:19 hi Dec 09 23:15:24 asac, could you please summarize the situation? Dec 09 23:15:50 situation is that the -codecs package failed because of relocation issue on armel ... adding -fPIC fixed that Dec 09 23:16:25 then that revealed that there seems to be some code built that isnt built on other archs in libavdecoder/aac.c Dec 09 23:16:37 this: http://pastebin.com/f65476f12 makes it build Dec 09 23:16:49 but i am not sure if its right ... though i saw other tests for that constant Dec 09 23:16:49 cool. Dec 09 23:16:58 so now it actually built here Dec 09 23:17:33 awong: so wonder if you know why -fPIC is not added for armel (though it is for amd64) Dec 09 23:17:41 or any reason not to add that on i386 too? Dec 09 23:17:45 e.g. everywhere? Dec 09 23:17:52 I actually do know the reason. :D Dec 09 23:17:58 cool. can you fix that ;)? Dec 09 23:18:04 i think -fPIC everywhere should be ok Dec 09 23:18:33 For arm, it's an oversight. We've only recently trying to fix the arm build. The -fPIC and -DPIC will probably get added soon (fbarchard has some changes in flight so I don't want to get into the mix quite yet). Dec 09 23:18:37 also please ccheck the patch above and commit that too if thats ok ;) ... so we get building packages Dec 09 23:18:47 hmm Dec 09 23:18:49 As for i386, -fPIC can't work. Dec 09 23:18:54 cant? Dec 09 23:18:56 nope. Dec 09 23:19:02 can you elaborate? Dec 09 23:19:05 Not unless you disable a whole bunch of the ffmpeg assembly. Dec 09 23:19:18 If you look at the current debian packages, -fPIC is actually disabled on ia32 builds of ffmpeg because of this. Dec 09 23:19:33 Basically, they need the extra register (ebx specifically) free to do some of their more optimized routines. Dec 09 23:19:37 i saw it wasnt used Dec 09 23:19:49 and thats why i thoght that adding everywhere is wrong as it felt intentional Dec 09 23:20:06 awong: so when is his arm work going to land? Dec 09 23:20:23 (fbarchard) Dec 09 23:20:54 i'll walk over and ask him in a sec... Dec 09 23:21:13 For your patch, if you could submit a crbug.com with the patch, that'd be the easiest way to get it committed. Dec 09 23:21:27 i hoped someone else can do that ;) Dec 09 23:21:29 http://dev.chromium.org/developers/contributing-code Dec 09 23:21:42 felt complicated when i last looked Dec 09 23:22:06 at least for drive-by contributors Dec 09 23:26:38 aac should be built for all arches with the non-free flags Dec 09 23:27:12 asac: the issue is that since it's your patch, we want to make sure the attribution is right. Dec 09 23:29:39 As for the arm stuff, fbarchard says he'll probably have something in a day or two. Dec 09 23:29:54 ok thanks. Dec 09 23:30:16 i dont even know where the ffmpeg code i patched is in svn ;) Dec 09 23:30:21 hah Dec 09 23:31:13 its not in third_party/ffmpeg for sure Dec 09 23:31:59 fta: where do you produce that ffmpeg-mt thing from? Dec 09 23:32:26 the tarballs inside the tarball? Dec 09 23:32:29 yes Dec 09 23:32:34 ffmpeg-mt Dec 09 23:32:40 i just get them from chromium Dec 09 23:32:44 where? Dec 09 23:32:44 untouched Dec 09 23:32:47 i dont see them in svn Dec 09 23:32:54 http://src.chromium.org/viewvc/chrome/trunk/src/third_party/ffmpeg/ Dec 09 23:33:23 http://src.chromium.org/svn/trunk/deps/third_party/ffmpeg/ Dec 09 23:33:28 yep, same Dec 09 23:33:32 nothingthere is nothing in it Dec 09 23:33:39 no libavdecoder/aac.c ;) Dec 09 23:34:51 http://src.chromium.org/viewvc/chrome/trunk/deps/third_party/ffmpeg/ Dec 09 23:34:54 its different Dec 09 23:34:57 crazy ;) Dec 09 23:35:06 so this whole patch is not possible ;) Dec 09 23:35:09 http://src.chromium.org/svn/trunk/deps/third_party/ffmpeg/patched-ffmpeg-mt/libavcodec/aac.c Dec 09 23:35:14 hmm Dec 09 23:35:19 yeah Dec 09 23:35:20 ok Dec 09 23:35:23 i can do that i hope Dec 09 23:35:24 ;) Dec 09 23:35:37 so, I can do the uploading of the patch and landing Dec 09 23:36:22 but I think you still need to follow a few of the steops in http://dev.chromium.org/developers/contributing-code about the Individual COntributor License Agreement, and getting your name into the Authors file. Dec 09 23:37:21 just for this minimal patch. cant you shuffle it a bit and then submit ;) Dec 09 23:37:35 hah. Dec 09 23:42:44 unforutnately, I don't htink that's quite cool. Frank's got a few changes for ARM in the air currently and will likely have fixed this same issue since it doesn't compile w/o it. Let's let his stuff land first and then we can hopefully just side-step this. Dec 09 23:43:44 it's silly, I know...but not being a lawyer, I don't know the consequences, blah blah. Dec 09 23:46:29 i now did all the gcl stuff ;) Dec 09 23:46:33 so you want me to abort that? Dec 09 23:46:33 heh Dec 09 23:47:29 up to you man. If you're most of the way there, I'm happy to review and land for you. Dec 09 23:48:25 awong: right. wonder if its a problem that i only checked out the libav*/ directory ... i assume gcl gets it right from svn info? Dec 09 23:48:38 btw, on your guys's build, are you doing the full gyp/make thing? If so...how are you building our ffmpeg for arm at all? I don't think we have a config.h checked in for arm. Dec 09 23:50:01 asac: I think gcl can handle it. However, bigger issue is that you're going to want to submit a patch to the source tree. Dec 09 23:50:26 and add it to http://src.chromium.org/svn/trunk/deps/third_party/ffmpeg/patches/to_upstream/ as patch 51. Dec 09 23:50:44 The "patched-ffmpeg-mt-source" directory is autogenerated from the tarball and these patches. Dec 09 23:50:47 right Dec 09 23:50:51 thats what i planned to do Dec 09 23:50:57 ah, ok Dec 09 23:51:05 you say on the patch in patches/? Dec 09 23:51:06 or both? Dec 09 23:51:13 oh Dec 09 23:51:48 only the patch in patches/? Dec 09 23:51:50 that was the question ;) Dec 09 23:51:51 sorry Dec 09 23:51:58 ah. yes, that's all you need. Dec 09 23:52:09 I'll regenerated the patches tree for you afterwards since Ihave everything already setup. Dec 09 23:52:22 ok ... good Dec 09 23:54:37 out for a few minutes getting some stuff Dec 09 23:55:36 np. I'm here for another hour or so. Othewrise, feel free to e-mail me (ajwong@chromium.org) Dec 10 01:38:25 ok lucid build still snaps Dec 10 01:38:26 :/ Dec 10 01:39:30 "pure virtual method called" still Dec 10 01:40:37 [6134:6134:3368164813:ERROR:/home/asac/chromium-browser-4.0.263.0~svn20091203r33682/build-tree/src/chrome/browser/renderer_host/render_sandbox_host_linux.cc(288)] Could not get pid Dec 10 01:40:48 saw that when running in gdm Dec 10 01:40:53 fta: ^ Dec 10 01:42:29 asac, hm, try with --disable-sandbox Dec 10 01:43:10 kk Dec 10 01:45:09 i thnk i have probs with /dev Dec 10 01:45:14 let me first sort that out Dec 10 01:57:59 fta: can you run chromium in a chroot well? Dec 10 01:58:20 never tried Dec 10 01:58:45 not sure the sandbox will work Dec 10 01:59:05 it does its own chroot **** ENDING LOGGING AT Thu Dec 10 02:59:56 2009