All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Microblaze gcc 4.5.0 support
Date: Mon, 17 May 2010 13:49:34 -0700	[thread overview]
Message-ID: <20100517204934.GE7932@gmail.com> (raw)
In-Reply-To: <AANLkTimIyO_fMaHX_tsssDwFNTLBBl3aFSaMmeBQHk_C@mail.gmail.com>

On (17/05/10 14:57), Adrian Alonso wrote:
> libgcc config.log http://pastebin.com/3mLhBMNP
> 
> <http://pastebin.com/3mLhBMNP>I see the error
> conftest.c:1:0: error: 'microblaze' is an invalid argument to -mcpu=

yeah :). So you know what to do next time you have a gcc configure error.
I think microblaze support is still on a branch in gcc. You
will be better off using the branch or get the diff of the
branch over gcc 4.5.0

-Khem



  reply	other threads:[~2010-05-17 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 18:38 Microblaze gcc 4.5.0 support Adrian Alonso
2010-05-17 19:01 ` Khem Raj
2010-05-17 19:14   ` Adrian Alonso
2010-05-17 19:18     ` Khem Raj
2010-05-17 19:29       ` Adrian Alonso
2010-05-17 19:41         ` Khem Raj
2010-05-17 19:57           ` Adrian Alonso
2010-05-17 20:49             ` Khem Raj [this message]
2010-05-18  0:47               ` Adrian Alonso

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=20100517204934.GE7932@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.