From: Daniel Jacobowitz <dan@debian.org>
To: Guido Guenther <agx@sigxcpu.org>, linux-mips@linux-mips.org
Subject: Re: 2.6 64bit kernels
Date: Sun, 28 Dec 2003 21:29:57 -0500 [thread overview]
Message-ID: <20031229022957.GA3652@nevyn.them.org> (raw)
In-Reply-To: <20031228195433.GH1298@bogon.ms20.nix>
On Sun, Dec 28, 2003 at 08:54:34PM +0100, Guido Guenther wrote:
> Hi,
> could anybody explain to me how one builds 2.6 (current CVS) 64bit
> kernel resulting in a 32bit ELF executable with a current (gcc >= 3.3,
> bintuils >= 2.14.90.0.5) toolchain.
> Major showstopper is that -Wa,-mabi=o64 doesn't work anymore, but
> -Wa,-mabi=32 -Wa,-mgp64 doesn't either since the assembler doesn't
> accept it.
> Thanks for any help,
I have found that the best way is to build a 64-bit ELF executable.
Then, use:
mips64_fp_le-objcopy -O elf32-ntradlittlemips vmlinux vmlinux.32bit
or the equivalent command.
You lose some space (lots) on wasted addressing calculations; no one
has found a good solution AFAIK.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-12-29 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 19:54 2.6 64bit kernels Guido Guenther
2003-12-28 20:01 ` ilya
2003-12-29 2:29 ` Daniel Jacobowitz [this message]
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=20031229022957.GA3652@nevyn.them.org \
--to=dan@debian.org \
--cc=agx@sigxcpu.org \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox