[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090102182248.GC10072@elte.hu>
Date: Fri, 2 Jan 2009 19:22:48 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
David Miller <davem@...emloft.net>, akpm@...ux-foundation.org,
rdreier@...co.com, ian.campbell@...rix.com,
jeremy.fitzhardinge@...rix.com, deller@....de,
rusty@...tcorp.com.au, linux-parisc@...r.kernel.org,
linux-kernel@...r.kernel.org, kyle@...artin.ca, randolph@...sq.org,
dave@...uly1.hia.nrc.ca
Subject: Re: [PATCH] kbuild: Disallow GCC 4.1.0 / 4.1.1
* Sam Ravnborg <sam@...nborg.org> wrote:
> > And it all looks more logical too, imho.
>
> Bugger....
> Now I cannot do cross compile for: alpha, arm, m68k and sparc.
hm, i just did a successful cross-build from x86 to alpha:
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
phoenix:~/linux/linux> head -6 /dev/shm/tip/build/.config
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.28
# Fri Jan 2 19:28:14 2009
#
CONFIG_ALPHA=y
with these commits present:
f9d1425: Disallow gcc versions 4.1.{0,1}
f153b82: Sanitize gcc version header includes
what type of cross-build breakage do they cause?
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists