10 May
2010
10 May
'10
3:32 a.m.
On Sunday 09 May 2010 23:22:19 Thomas Bächler wrote:
Am 09.05.2010 19:37, schrieb Thomas Bächler:
Am 09.05.2010 19:23, schrieb Pierre Schmitz:
I noticed the same. But this is caused by the mkinitcpio update and not the kernel. In my case "logo.nologo" in the kernel parameter line was causing this.
That is plan bullshit. The mkinitcpio update didn't even _touch_ the init file, it is entirely unchanged.
Okay, gcc 4.5.0 still fucks up, I am pushing a new mkinitcpio-busybox directly to core, built with -O0 this time, as this will keep breaking people's systems.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43987 is that related? -- Regards Shridhar