From: Simon Horman <horms@verge.net.au>
To: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Cc: "Edgar E. Iglesias" <edgar@axis.com>,
kexec@lists.infradead.org, jespern@axis.com
Subject: [patch] cris: add cris architecture to configure
Date: Wed, 8 Oct 2008 17:19:35 +1100 [thread overview]
Message-ID: <20081008061933.GI22396@verge.net.au> (raw)
In-Reply-To: <20081008061541.GF22396@verge.net.au>
# PATH=$PATH:/usr/local/cris/bin/ CC=crisv32-axis-linux-gnu-gcc \
./configure --host=crisv32-axis-linux-gnu
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking build system type... i686-pc-linux-gnu
checking host system type... cris-axis-linux-gnu
checking target system type... cris-axis-linux-gnu
configure: error: unsupported architecture cris
Signed-off-by: Simon Horman <horms@verge.net.au>
---
configure.ac | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
I have added this patch to the kexec-tools git tree.
diff --git a/configure.ac b/configure.ac
index ff3b304..c9793b6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -42,7 +42,7 @@ case $target_cpu in
mips|mipsel )
ARCH="mips"
;;
- crisv32 )
+ cris|crisv32 )
ARCH="cris"
;;
ia64|x86_64|alpha )
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2008-10-08 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 14:08 [PATCH] cris: Add CRISv32 support Edgar E. Iglesias
2008-09-05 0:42 ` Simon Horman
2008-09-05 9:25 ` Edgar E. Iglesias
2008-10-08 6:15 ` Simon Horman
2008-10-08 6:17 ` [PATCH] Only use -fno-zero-initialized-in-bss if it is available Simon Horman
2008-10-08 6:18 ` [PATCH] cris: add kexc_load syscall Simon Horman
2008-10-08 6:19 ` Simon Horman [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=20081008061933.GI22396@verge.net.au \
--to=horms@verge.net.au \
--cc=edgar.iglesias@axis.com \
--cc=edgar@axis.com \
--cc=jespern@axis.com \
--cc=kexec@lists.infradead.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