[10:36] <erikcorry> gcc 4.4.1 seems to be generating some screwy code for me.
[10:37] <erikcorry> Is there a newer release I could try?
[11:10] <lool> erikcorry: Is this reported?
[11:10] <lool> erikcorry: 4.4.1 is the latest we have, but we add patches
[11:12] <erikcorry> I'm trying to reduce it.
[11:12] <erikcorry> Fails to compile Google V8
[11:12] <erikcorry> In -O2 mode
[11:13] <erikcorry> I already added -fno-strict-aliasing
[14:02] <erikcorry> Gotcha.
[14:02] <erikcorry> Who should I mail the reduced test case to?
[14:02] <lool> erikcorry: Upstream?  :-)
[14:02] <erikcorry> Or should I just file a bug on gcc's site?
[14:02] <lool> erikcorry: I'd file a bug against gcc-4.4 upstream
[14:03] <lool> Yeah
[14:03] <erikcorry> It only happens with -O3
[14:04] <lool> erikcorry: You could find out which subopt breaks it
[14:04] <lool> erikcorry: gcc -c -Q -Os --help=optimizers will give you a list
[14:04] <erikcorry> Thx
[14:04] <lool> or -O3
[14:05] <erikcorry> Woah!
[14:05] <erikcorry> 163 optimizations!
[14:05] <lool> erikcorry: Have fun  :)
[14:05] <ogra> thats what these gentoo guys say too all the time ;)
[14:05] <ogra> and they they switch them all on ;)
[14:25] <erikcorry> -fno-tree-sink makes it go away.
[14:26] <erikcorry> That's actually part of -O1
[16:54] <jalto> hey guys, the latest rootstock is hanging for me on startup complaining about rsyslogd
[16:54] <jalto> pastebin at : http://pastebin.com/m21cd01a3
[16:55] <ogra> looks like a dbus issue
[16:55] <ogra> is that during build or the installed rootfs on a machine ?
[16:56] <jalto> it's on an sd card, so during startup of the sheevaplug that I am running it off of
[16:56] <jalto> build was successful
[16:56] <ogra> what release did you build ?
[16:56] <ogra> jaunty or karmic
[16:57] <jalto> karmic
[16:57] <ogra> karmic wont run on sheeva ... its ARMv6 now
[16:58] <jalto> oh ok
[16:58] <ogra> we use -march=armv6 -mfloat-abi=softfp and -mfpu=vfp now
[16:58] <jalto> I'm guessing it's the same for debian?
[16:58] <ogra> so thats likely where your illegal instruction comes from ...
[16:58] <ogra> no
[16:58] <ogra> debian uses v5 or even something smaller afaik
[16:59] <jalto> so the img files that are build for ubuntu are all armv6 as well then
[17:00] <lool> jalto: for karmic
[17:00] <lool> but yes
[17:01] <jalto> alright that's for the help
[17:01] <ogra> jaunty will work on your sheeva though
[17:01] <lool> jalto: jaunty is fine though
[17:02] <jalto> I was having trouble with rootstock for jaunty as well, but I need to revisit it and report back
[17:02] <ogra> yes, tell me if you run into any issues
[18:11] <jalto> ogra, I tried to get jaunty up and running and it hangs on starting kernel log daemon
[18:12] <jalto> the kernel I'm using comes from http://sheeva.with-linux.com/sheeva/
[18:12] <ogra> jalto, did you enable a serial console ?
[18:12] <jalto> 2.6.30.5
[18:13] <jalto> in grub?
[18:13] <ogra> in rootstock :)
[18:13] <ogra> it has a --serial option, else the system wont set up serial in init
[18:14] <ogra> i.e the only login prompt you would see after starting klogd would be on a VGA output ...
[18:14] <ogra> which is hard to get in a sheeva i imagine
[18:15] <jalto> ogra thanks a tty might be useful
[18:15] <ogra> the other option is to have openssh-server installed and know the IP
[18:15] <ogra> so you can log in via ssh
[18:16] <jalto> back to building
[18:16] <ogra> do you have your tgz around ?
[18:17] <ogra> just untar it in a dir ...
[18:17] <ogra> https://wiki.ubuntu.com/ARM/BuildEABIChroot ...
[18:17] <ogra> chroot into it and install openssh-server
[18:17] <ogra> (and set up /etc/network/interfaces if needed)
[18:18] <ogra> there are jaunty packages in my ppa
[18:18] <jalto> thanks it's on an sd card so I can just pop it into my desktop and play with it
[18:19] <ogra> yeah
[18:19] <ogra> note that qemu-arm-static doesnt work with mono packages yet ... in case oyu plan to do any mono stuff
[18:43] <jalto> ogra, it pinged fine, but my build doesn't have an /etc/ssh folder with configs, so it wouldn't accept ssh
[18:44] <jalto> not sure if ssh was installed
[18:45] <ogra> its not by default
[18:46] <ogra> if you didnt add it to the --seed option
[18:46] <ogra> if you install it through qemu-arm-static you need to make sure /proc is mounted inside your chroot
[18:46] <ogra> else it wont generate keys
[18:46] <ogra> (and make sure to unmount /proc again afterwards)
[18:47] <jalto> ok
[18:48] <jalto> well the fact that it pinged was a good sign
[18:48] <ogra> indeed
[18:49] <ogra> anyway, its getting late here, i'll go afk now ...
[18:50] <jalto> good night
[18:50] <jalto> and thanks for the help
[18:50] <ogra> see you around (i hope) ;)
[22:22] <ali12341> ogra: just noticed something about my console-kit-dae problem
[22:22] <ali12341> on dmesg: console-kit-dae invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
[22:23] <ali12341> it seems like the oomkiller killed it, but it still lives on and eats all cpu...
[22:26] <lool> Hmm
[22:27] <lool> ali12341: Would be best to start afresh and monitor what's happening on a fresh system; could be a process eating all the RAM, being killed and then another one using all CPU waiting for it
[22:27] <ali12341> that happened during boot
[22:27] <ali12341> this machine only has 64mb
[22:28] <lool> Ah that might be why
[22:28]  * lool sleep &
[22:28] <ali12341> it seems like actually gdm got killed
[22:33] <ali12341> the funny thing is i can actually log in to the desktop and everything works more or less
[22:33] <ali12341> it's really slow though, due to the runaway process