From: Andi Kleen <ak@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc4 warning on arch/x86_64/boot/compressed/head.o
Date: Wed, 9 Aug 2006 09:09:19 +0200 [thread overview]
Message-ID: <200608090909.19985.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0608090823570.11585@yvahk01.tjqt.qr>
On Wednesday 09 August 2006 08:26, Jan Engelhardt wrote:
> >> Compiling 2.6.18-rc4 on x86_64 gets this warning.
> >>
> >> gcc -Wp,-MD,arch/x86_64/boot/compressed/.head.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-suse-linux/4.1.0/include -D__KERNEL__ -Iinclude -Iinclude2 -I$KBUILD_OUTPUT/linux/include -include include/linux/autoconf.h -D__ASSEMBLY__ -m64 -traditional -m32 -c -o arch/x86_64/boot/compressed/head.o $KBUILD_OUTPUT/linux/arch/x86_64/boot/compressed/head.S
> >> ld -m elf_i386 -Ttext 0x100000 -e startup_32 -m elf_i386 arch/x86_64/boot/compressed/head.o arch/x86_64/boot/compressed/misc.o arch/x86_64/boot/compressed/piggy.o -o arch/x86_64/boot/compressed/vmlinux
> >> ld: warning: i386:x86-64 architecture of input file `arch/x86_64/boot/compressed/head.o' is incompatible with i386 output
> >
> >It always gave that since some binutils update long ago.
> >If you know how to fix it please submit a patch, but as far as I know it's harmless.
>
> Why is -m elf_i386 passed to ld?
> I suppose because this is necessary because AMD64 starts in i386 16-bit
> real mode?
> Might try -m elf32-little or -m elf64-little.
If you think you have a solution please submit a tested patch.
-Andi
next prev parent reply other threads:[~2006-08-09 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 2:47 2.6.18-rc4 warning on arch/x86_64/boot/compressed/head.o Keith Owens
2006-08-08 2:55 ` Andi Kleen
2006-08-09 6:26 ` Jan Engelhardt
2006-08-09 7:09 ` Andi Kleen [this message]
2006-08-10 7:23 ` Jan Engelhardt
2006-08-15 13:11 ` Jan Engelhardt
2006-08-15 14:07 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608090909.19985.ak@suse.de \
--to=ak@suse.de \
--cc=jengelh@linux01.gwdg.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.