From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: binutils@sourceware.org
Subject: Re: [PATCH] [MIPS] Add mips*el-rtems stubs
Date: Mon, 31 Dec 2012 13:49:00 -0000 [thread overview]
Message-ID: <50E19735.5000303@rtems.org> (raw)
In-Reply-To: <1356947278182-217630.post@n7.nabble.com>
On 12/31/2012 10:47 AM, Devin wrote:
> Hi,all.
> According to Liu's Changelog, I change same content in 1,/bfd/config.bfd
> 2,/gas/configure.tgt 3/ld/configure.tgt ,just like what Liu changed.
> and then , I have not changed anything. I build the toolchain like
> "mipsel-rtems-gcc",but when I configure RTEMS. It does not appear
> information like :
> /target architecture: mips.
> available BSPs: hurricane.
> 'gmake all' will build the following BSPs: hurricane.
> other BSPs can be built with 'gmake RTEMS_BSP="bsp1 bsp2 ..."'/
> my configure command is
> "../rtems-4.10.2/configure --target=mipsel-rtems --quiet --disable-posix
> --disable-networking --disable-cxx --disable-itron
> --enable-rtemsbsp="hurricane" --prefix=/opt/mipsel "
> what happend about this?
> thanks a lot !
This question of off-topic for this list.
To answer your question: mipsel-rtems is not a valid target tuple.
a) The RTEMS source tree doesn't support a "mipsel" cpu.
It expects little endian mips as a multilib-variant of the "mips" cpu.
b) The OS name is supposed to carry a version number (-rtems4.10,
rtems4.11 etc.). Non-versioned OS names are not supported.
Ralf
next prev parent reply other threads:[~2012-12-31 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 6:26 Jia Liu
2012-10-30 11:21 ` Richard Sandiford
2012-10-30 12:19 ` Ralf Corsepius
2012-12-31 9:48 ` Devin
2012-12-31 13:49 ` Ralf Corsepius [this message]
2013-01-04 3:06 ` Devin
2012-10-30 12:25 Joel Sherrill
2012-10-30 13:52 ` Jia Liu
2012-12-07 1:12 ` Jia Liu
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=50E19735.5000303@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).