On Mon, Jan 02, 2012 at 04:58:20PM +0100, Joerg Roedel wrote:

On Tue, Jan 03, 2012 at 12:21:30AM +0900, KyongHo Cho wrote:

quoted

quoted

I still get

?LD ? ? ?.tmp_vmlinux1
/data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no machine record defined
/data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no machine record defined
/data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no machine record defined
make[1]: *** [.tmp_vmlinux1] Error 1

when trying to compile ARM/Exynos with 3.2-rc7. Am I doing something
wrong or is this not expected to work?

Do you?
Ok. I will check my configuration with linux-next git.

Compiling my exynos-config with linux-next gives me:

  CC      arch/arm/kernel/process.o
In file included from /data/lemmy/linux.trees.git/arch/arm/mach-exynos/include/mach/system.h:16:0,
                 from /data/lemmy/linux.trees.git/arch/arm/kernel/process.c:64:
/data/lemmy/linux.trees.git/arch/arm/plat-samsung/include/plat/system-reset.h:19:2: error: #error Fix me up

I better not ask the question how such an #error statement can come
through to linux-next.

It comes through when I stick it in my tree because of a month of asking
for help to fix something and getting zero response from the maintainers.

It's a way to flag to them that they're doing something wrong - and in
fact something is broken, and that that brokenness will happen at the
next merge window unless they get off their butt and do something about
it.

Patches have been around, but I've had problems merging them, and the
replacement patches have now appeared after I started my Christmas
vacation.  As I've just returned, it's going to be a couple of days
before the #error gets removed (assuming the replacement patches apply.)