Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [MIPS] toolchain/gcc/Config.in broken
Date: Tue, 9 Oct 2007 18:30:49 +0200	[thread overview]
Message-ID: <20071009163049.GA16889@aon.at> (raw)
In-Reply-To: <470B88CC.9040705@ruby.dti.ne.jp>

On Tue, Oct 09, 2007 at 10:57:32PM +0900, Shinya Kuribayashi wrote:
> Bernhard Fischer wrote:
>>> [1] mips: Before recently toolchain config rework (2007-09-19 build)
> <snip>
>> I don't know offhand what abi that defaults to. Can you check this,
>> perhaps?
>
> Yes, confirmed with r19885 (2007-09-18).
> At that time, we used to configure ABI and ISA as a uClibc config,
> right? I always configured O32 ABI and MIPS32, no doubt:

> But it seems these configs were not directly passed to GCC configs
> according to mips-linux-gcc -v, or GCC config.status.

Yes, that's what my recent changes in this area are ment to pin.

Please use 32 manually for now. I'll look at it ASAP.

  reply	other threads:[~2007-10-09 16:30 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 [this message]
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
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=20071009163049.GA16889@aon.at \
    --to=rep.dot.nop@gmail.com \
    --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