From: Michael Pruznick <michael_pruznick@mvista.com>
To: linux-mips@linux-mips.org
Subject: PATCH:2.4:CONFIG_BINFMT_IRIX
Date: Tue, 05 Aug 2003 12:25:01 -0600 [thread overview]
Message-ID: <3F2FF67D.8B0C2DFB@mvista.com> (raw)
All this does is put "CONFIG_BINFMT_IRIX is not set" into the
config files so that when switching dual-endian systems from LE
to BE this will default to "n" instead of "y".
The main problem with this is that, in general, there is no
need/desire to have CONFIG_BINFMT_IRIX included just because
the kernel is BE. Rather than being forced to disable this,
I think the default should be off.
In some older kernels, it this causes compile errors, but that
problem doesn't seam to exit in the latest 2.4 tree.
I tested this with menuconfig and xconfig.
I'm not an expert in all the subtle dependencies issues with
the config.in files so there may be a better way do to this.
cvs diff -uN arch/mips/config-shared.in
Index: arch/mips/config-shared.in
===================================================================
RCS file: /home/cvs/linux/arch/mips/Attic/config-shared.in,v
retrieving revision 1.1.2.80
diff -u -r1.1.2.80 config-shared.in
--- arch/mips/config-shared.in 5 Aug 2003 11:13:39 -0000 1.1.2.80
+++ arch/mips/config-shared.in 5 Aug 2003 17:07:24 -0000
@@ -817,6 +817,8 @@
if [ "$CONFIG_CPU_LITTLE_ENDIAN" = "n" ]; then
bool 'Include IRIX binary compatibility' CONFIG_BINFMT_IRIX
+else
+ define_bool CONFIG_BINFMT_IRIX n
fi
if [ "$CONFIG_CPU_R10000" = "y" ]; then
next reply other threads:[~2003-08-05 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 18:25 Michael Pruznick [this message]
2003-08-07 18:02 ` PATCH:2.4:CONFIG_BINFMT_IRIX Michael Pruznick
2003-08-07 18:37 ` PATCH:2.4:CONFIG_BINFMT_IRIX Guido Guenther
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=3F2FF67D.8B0C2DFB@mvista.com \
--to=michael_pruznick@mvista.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 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.