**** BEGIN LOGGING AT Sun Dec 13 02:59:57 2009
Dec 13 08:26:40 <keesj> Hi, I want to get started on ubutunu-arm. I currently want to target qemu-arm versatile (possibly using the arm11 cpu) and would like to use 9.10 and rootstock. Would this be recommented (elinux.org has a "ok" turorial when using beagle + rootstock the topic links on this irc channel point to what looks to the old way of doing things)
Dec 13 10:04:55 <lool> keesj: this is incompatible
Dec 13 10:05:56 <lool> keesj: It can work with a patched versatile kernel though
Dec 13 10:06:33 <lool> keesj: I think there is such a kernel in the development release now, or you can get some binary ones in some places
Dec 13 10:07:01 <lool> keesj: Just FYI, the real hardware named "versatile" which qemu emulates only supports up to v5 ATM
Dec 13 11:03:08 <armin76> lool: question: now that karmic is the latest released version, does that mean that jaunty doesn't get any update anymore?
Dec 13 13:26:40 <lool> armin76: In terms of where developers spend their time, I don't think many stable updates will happen in jaunty, it's not impossible but unlikely; but of course security support continues and if critical bug fixes need to be addressed in jaunty they can be
Dec 13 13:26:58 <lool> armin76: Even at this point, karmic is much less of a focus than lucid
Dec 13 13:49:21 <armin76> lool: ack, thanks
Dec 13 14:04:32 <asac> ogra: yes ... my install feels good too ... thats t2 maybe?;)
Dec 13 14:28:41 <asac> fta: chromium codecs fails on i386?
Dec 13 14:28:46 <asac> wanted to copy it
Dec 13 14:28:52 <fta> asac, please don't.
Dec 13 14:29:03 <fta> asac, http://code.google.com/p/gyp/issues/detail?id=123
Dec 13 14:29:07 <asac> sure
Dec 13 14:29:13 <asac> i wont copy if the build fails ;)
Dec 13 14:29:43 <asac> fta: would that impact arm?
Dec 13 14:29:47 <fta> asac, last comment
Dec 13 14:29:55 <fta> probably yes
Dec 13 14:30:23 <asac> why did you switch to make just now :(
Dec 13 14:30:32 <fta> i thought it was ready
Dec 13 14:30:35 <asac> can i disable that manually again?
Dec 13 14:30:45 <asac> e.g. just a single rules line?
Dec 13 14:31:59 <fta> I don't have common.gypi in this package so most variables have no default during the build (like target_arch, chromeos, branding, library, and guess what.. cflags and ldflags), so i set those in GYP_DEFINES, but it doesn't work for cflags/ldflags.  The build fails with an asm error (the fix is to add the missing -O2) but if i set CFLAGS=-O2, it breaks all the defines and the -I.
Dec 13 14:33:35 <fta> nope, it will be the same with scons (unlike for chromium)
Dec 13 14:41:15 <fta> asac, ^^, testing my proposed fix right now
Dec 13 14:43:14 <asac> what changed that even scons suddenly doesnt work anymore?
Dec 13 14:45:13 <fta> scons would work if i also ship the whole src/build/ dir from chromium in the codecs package (and probably other dirs), while i just took the ffmpeg.gyp file, which is enough, in theory
Dec 13 14:46:34 <fta> i just loose the defaults, so i have to specify them as i said above
Dec 13 14:47:17 <fta> what happens if is say gcc -O2 -Os ? which one is used?
Dec 13 14:47:33 <fta> -is+I
Dec 13 14:48:05 <asac> feels not right to "loose defaults" ... they might do arch dependent tweaks etc.
Dec 13 14:48:25 <asac> i dont think we want to duplicate all defaults in rules
Dec 13 14:48:35 <asac> feels like not running configure
Dec 13 14:48:54 <fta> that's the whole point of this gyp, not run configure
Dec 13 14:49:10 <fta> gyp is a configure rival
Dec 13 14:49:37 <fta> in python :S
Dec 13 14:50:25 <fta> and upstream is dropping support for scons anyway, so the sooner i move, the better
Dec 13 14:50:33 <asac> right. but i expect that the defaults contain detection stuff etc.
Dec 13 14:50:57 <asac> yes. but you dropped the defaults ... which feels like a bug
Dec 13 15:00:42 <keesj> lool I will be able to create a kernel if needed. still rootstock + qemu-system-arm should be easy right?
Dec 13 15:08:27 <fta> asac, i'm pretty conservative here. missing defaults make gyp fail, so it FTBFS for us and we notice. And i set only those: GYP_DEFINES="target_arch=ia32 chromeos=0 branding=Chromium library=static_library use_system_yasm=1". The only problem is cflags/lflags that dpkg-buildpackage wants to overwrite
Dec 13 15:12:08 <fta> asac, if i really want to pull src/build too, that would mean 3 svn to pull to create the tarball.
Dec 13 15:13:46 <fta> asac, i already name my stuff 0.5+svn20091210r34297+34315, i can add a 3rd rev-id :P that would mean rebuilding more often (for any commit in src/build, even totally unrelated)
Dec 13 15:15:36 <fta> i should start a contest of the longest version ever used for a package
Dec 13 15:35:16 <lool> keesj: Yes
Dec 13 15:48:26 <keesj> thanks
Dec 13 15:49:51 <asac> fta: isnt it like "extra_cflags=..:" ?
Dec 13 15:51:53 <fta> asac, no, not without src/build :(
Dec 13 16:21:46 <fta> asac, chromium-codecs-ffmpeg_0.5+svn20091210r34297+34315+34433.orig.tar.gz uhuh
Dec 13 16:22:31 <asac>       self.WriteLn("$(OBJS): CFLAGS := $(CFLAGS_$(BUILDTYPE)) "
Dec 13 16:22:34 <asac> shouldnt that be
Dec 13 16:22:38 <asac>       self.WriteLn("$(OBJS): CFLAGS += $(CFLAGS_$(BUILDTYPE)) "
Dec 13 16:22:39 <asac> ?
Dec 13 16:22:55 <asac> in make.py
Dec 13 16:22:57 <asac> (gyp)
Dec 13 16:23:07 <fta> won't work, as make CFLAGS="-g -O2" would overwrite it anyway
Dec 13 16:23:32 <asac> += ?
Dec 13 16:23:43 <fta> yes
Dec 13 16:24:04 <fta> asac, http://paste.ubuntu.com/340609/
Dec 13 16:24:55 <asac> yes thats ok too
Dec 13 17:47:16 <fta> asac, i'm done fixing the codecs
Dec 13 19:10:05 <fta> asac, you can copy the codecs now, they are all green in lucid. you need to copy gyp too (a new build-dep)
**** ENDING LOGGING AT Mon Dec 14 02:59:56 2009