All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 -> x86_64 cross compile failure (binutils bug?)
Date: Fri, 23 Dec 2005 00:59:04 -0500	[thread overview]
Message-ID: <1135317544.4473.17.camel@mindpipe> (raw)
In-Reply-To: <20051211000039.GR11190@wotan.suse.de>

On Sun, 2005-12-11 at 01:00 +0100, Andi Kleen wrote:
> > Here are the relevant lines of arch/x86_64/kernel/vmlinux.lds:
> > 
> >     382 OUTPUT_FORMAT("elf64-x86-64", "elf64-x86-64", "elf64-x86-64")
> >     383 OUTPUT_ARCH(1:x86-64)
> >     384 ENTRY(phys_startup_64)
> > 
> > Any ideas?  Another toolchain quirk?
> 
> The original is 
> 
> OUTPUT_ARCH(i386:x86-64)
> 
> It replaced the i386 with 1, which obviously doesn't work.
> 
> Try (full patch again) 
> 

I still get:

  SYSCALL arch/x86_64/ia32/vsyscall-sysenter.so
/usr/bin/ld: warning: i386:x86-64 architecture of input file
`arch/x86_64/ia32/vsyscall-sysenter.o' is incompatible with i386 output
  AS      arch/x86_64/ia32/vsyscall-syscall.o
  SYSCALL arch/x86_64/ia32/vsyscall-syscall.so
/usr/bin/ld: warning: i386:x86-64 architecture of input file
`arch/x86_64/ia32/vsyscall-syscall.o' is incompatible with i386 output
  AS      arch/x86_64/ia32/syscall32_syscall.o

Lee



  parent reply	other threads:[~2005-12-23  5:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 18:50 i386 -> x86_64 cross compile failure (binutils bug?) Lee Revell
2005-12-09 19:50 ` Ken Moffat
2005-12-09 19:59   ` Lee Revell
2005-12-09 21:30     ` Ken Moffat
2005-12-09 21:40       ` Lee Revell
2005-12-09 22:19         ` Ken Moffat
2005-12-09 19:58 ` Kyle McMartin
2005-12-09 20:21   ` Lee Revell
2005-12-09 20:41     ` Kyle McMartin
2005-12-09 20:58       ` Lee Revell
2005-12-09 21:25         ` Steven Rostedt
2005-12-09 21:35           ` Lee Revell
2005-12-09 21:10       ` Lee Revell
2005-12-09 21:19         ` Kyle McMartin
2005-12-09 22:37 ` Jeffrey Hundstad
2005-12-10  0:05   ` Lee Revell
2005-12-10  0:23     ` Jeffrey Hundstad
2005-12-10  1:28       ` Lee Revell
2005-12-10  1:50       ` Lee Revell
2005-12-10  8:56         ` Andi Kleen
2005-12-10  5:12           ` Lee Revell
2005-12-10  7:19             ` Andi Kleen
2005-12-10  7:43               ` Lee Revell
2005-12-10 19:34               ` Lee Revell
2005-12-11  0:00                 ` Andi Kleen
2005-12-11  0:26                   ` Lee Revell
2005-12-16 23:40                   ` Lee Revell
2005-12-23  5:59                   ` Lee Revell [this message]
2006-01-11 16:48                   ` Lee Revell
2006-01-11 16:54                     ` Andi Kleen
2005-12-09 22:43 ` Xavier Bestel
2005-12-10  1:31   ` Lee Revell
2005-12-10 20:34     ` Xavier Bestel
2005-12-10 20:48       ` Lee Revell

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=1135317544.4473.17.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=ak@suse.de \
    --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.