From: Elizabeth Oldham <beth@the-hug.org>
To: buildroot@busybox.net
Subject: [Buildroot] [MIPS] toolchain/gcc/Config.in broken
Date: Tue, 09 Oct 2007 21:56:40 +0100 [thread overview]
Message-ID: <470BEB08.3060209@the-hug.org> (raw)
In-Reply-To: <470BD9AB.2020909@the-hug.org>
Elizabeth Oldham wrote:
> Bernhard Fischer wrote:
>>> o32 n32 n64
>>>MIPS I o
>>>MIPS II o
>>>MIPS III o o o
>>>MIPS IV o o o
>>>MIPS32(r1) o
>>>MIPS32R2 o
>>>MIPS64(r1) o o o
>>>MIPS64R2 o o o
>>>(blank is not supported)
> I'm not familar with eabi, I've not heard of it with reference to MIPS.
> I'd have to ask my more learned colleagues :)
gcc supports it, but AFAIK it isn't used on MIPS/Linux, so I assume
buildroot/uclibc wont be interested in it?
> Once you have a supported ISA/ABI you can choose your endian with impunity.
Or vice-versa.
I've hacked target/Config.in.arch to what I _think_ it should perhaps
look like, and attached it.
Beth
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Config.in.arch.patch
Url: http://busybox.net/lists/buildroot/attachments/20071009/423c9a47/attachment.diff
next prev parent reply other threads:[~2007-10-09 20:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <470ADDA8.3080105@ruby.dti.ne.jp>
2007-10-09 7:08 ` [Buildroot] [MIPS] toolchain/gcc/Config.in broken Bernhard Fischer
2007-10-09 9:56 ` Shinya Kuribayashi
2007-10-09 12:27 ` Bernhard Fischer
2007-10-09 13:57 ` Shinya Kuribayashi
2007-10-09 16:30 ` Bernhard Fischer
2007-10-09 19:16 ` Elizabeth Oldham
2007-10-09 19:33 ` Bernhard Fischer
2007-10-09 19:42 ` Elizabeth Oldham
2007-10-09 20:56 ` Elizabeth Oldham [this message]
2007-10-09 21:31 ` Bernhard Fischer
2007-10-10 2:52 ` Shinya Kuribayashi
[not found] ` <120071009213155.GU20951@aon.at>
2007-10-10 10:13 ` Elizabeth Oldham
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=470BEB08.3060209@the-hug.org \
--to=beth@the-hug.org \
--cc=buildroot@busybox.net \
/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