From: Martin Michlmayr <tbm@cyrius.com>
To: linux-mips@linux-mips.org
Subject: Re: CONFIG_64BIT and CONFIG_BUILD_ELF64
Date: Wed, 18 Jan 2006 14:10:59 +0000 [thread overview]
Message-ID: <20060118141059.GU6827@deprecation.cyrius.com> (raw)
In-Reply-To: <20060118125127.GA3555@linux-mips.org>
* Ralf Baechle <ralf@linux-mips.org> [2006-01-18 12:51]:
> At this stage support for gcc 2.95 is decaying and soon may be removed
> entirely from the kernel. So the time to hardwire CONFIG_BUILD_ELF64=y
> may have come.
[mips] Enable BUILD_ELF64 when 64BIT is set
New toolchain does not support building 32-bit ELF objects with 64-bit
code, so we enable BUILD_ELF64 when 64bit is on.
Ralf Baechle: "At this stage support for gcc 2.95 is decaying and soon
may be removed entirely from the kernel. So the time to hardwire
CONFIG_BUILD_ELF64=y may have come."
Signed-off-by: Martin Michlmayr <tbm@cyrius.com>
---
Kconfig | 12 +-----------
1 file changed, 1 insertion(+), 11 deletions(-)
--- linux-mips/arch/mips/Kconfig 2006-01-10 11:21:15.000000000 +0000
+++ new/arch/mips/Kconfig 2006-01-18 14:07:15.000000000 +0000
@@ -1722,17 +1722,7 @@
config BUILD_ELF64
bool "Use 64-bit ELF format for building"
depends on 64BIT
- help
- A 64-bit kernel is usually built using the 64-bit ELF binary object
- format as it's one that allows arbitrary 64-bit constructs. For
- kernels that are loaded within the KSEG compatibility segments the
- 32-bit ELF format can optionally be used resulting in a somewhat
- smaller binary, but this option is not explicitly supported by the
- toolchain and since binutils 2.14 it does not even work at all.
-
- Say Y to use the 64-bit format or N to use the 32-bit one.
-
- If unsure say Y.
+ default y
config BINFMT_IRIX
bool "Include IRIX binary compatibility"
--
Martin Michlmayr
http://www.cyrius.com/
next prev parent reply other threads:[~2006-01-18 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 12:31 CONFIG_64BIT and CONFIG_BUILD_ELF64 Martin Michlmayr
2006-01-18 12:42 ` Maciej W. Rozycki
2006-01-18 12:51 ` Ralf Baechle
2006-01-18 14:10 ` Martin Michlmayr [this message]
2006-01-18 14:12 ` Stephen P. Becker
2006-01-18 14:20 ` Maciej W. Rozycki
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=20060118141059.GU6827@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--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