From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 -> x86_64 cross compile failure (binutils bug?)
Date: Fri, 09 Dec 2005 18:23:57 -0600 [thread overview]
Message-ID: <439A201D.7030103@mnsu.edu> (raw)
In-Reply-To: <1134173138.18432.41.camel@mindpipe>
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
Lee Revell wrote:
>On Fri, 2005-12-09 at 16:37 -0600, Jeffrey Hundstad wrote:
>
>
>>Lee Revell wrote:
>>
>>
>>
>>>I'm trying to build an x66-64 kernel on a 32 bit system (Ubuntu 5.10).
>>>I added -m64 to the CFLAGS as per the gcc docs. But the build fails
>>>with:
>>>
>>>$ make ARCH=x86_64
>>> [...]
>>> CC init/initramfs.o
>>>
>>>
>>>
>>>
>>I have successfully done this using Debian/Sid.
>>
>>
>>
>
>I added "-m64" to AFLAGS as well and now I get farther:
>
> CC arch/x86_64/ia32/syscall32.o
> AS arch/x86_64/ia32/vsyscall-sysenter.o
>arch/x86_64/ia32/vsyscall-sysenter.S: Assembler messages:
>arch/x86_64/ia32/vsyscall-sysenter.S:14: Error: suffix or operands invalid for `push'
>arch/x86_64/ia32/vsyscall-sysenter.S:16: Error: suffix or operands invalid for `push'
>arch/x86_64/ia32/vsyscall-sysenter.S:18: Error: suffix or operands invalid for `push'
>arch/x86_64/ia32/vsyscall-sysenter.S:25: Error: suffix or operands invalid for `pop'
>arch/x86_64/ia32/vsyscall-sysenter.S:27: Error: suffix or operands invalid for `pop'
>arch/x86_64/ia32/vsyscall-sysenter.S:29: Error: suffix or operands invalid for `pop'
>arch/x86_64/ia32/vsyscall-sigreturn.S:16: Error: suffix or operands invalid for `pop'
>make[1]: *** [arch/x86_64/ia32/vsyscall-sysenter.o] Error 1
>make: *** [arch/x86_64/ia32] Error 2
>
>Lee
>
>
>
Yes, some commands NEED the -m64 and and WILL NOT work with -m64.
Really, try my method. I've done it without all that making a separate
binutils non-sense.
You do need the 64-bit Debian build tools and 64 bit libraries. These
are the ones I have:
amd64-libs
amd64-libs-dev
lib64gcc1
lib64gfortran0
lib64ncurses5
lib64ncurses5-dev
lib64objc1
lib64stdc++6
lib64stdc++6-4.0-dbg
lib64z1
lib64z1-dev
libc6-amd64
libc6-dev-amd64
Yes... here's lin64.tar.gz if you didn't catch my little scripts before.
BTW: if there's a better way, please let me know. ...After I got this
to work I kinda quit looking ;-)
--
Jeffrey Hundstad
[-- Attachment #2: lin64.tar.gz --]
[-- Type: application/gzip, Size: 354 bytes --]
next prev parent reply other threads:[~2005-12-10 0:23 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 [this message]
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
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=439A201D.7030103@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox