public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support
Date: Mon, 24 Aug 2009 13:56:48 +0200	[thread overview]
Message-ID: <20090824115648.84C5C833DBD2@gemini.denx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202E3915D8B@SC-VEXCH1.marvell.com>

Dear Prafulla Wadaskar,

In message <73173D32E9439E4ABB5151606C3E19E202E3915D8B@SC-VEXCH1.marvell.com> you wrote:
> 
> > Hm... aren't there known issues with these compiler versions on ARM?
> I don't think so, I observed same behavior with sheevaplug,

Which tool chain are you using? Do you see differnt behaviour with
and without USE_PRIVATE_LIBGCC=yes ?

> i.e. "nand_bbt: Can't scan flash and build the RAM-based BBT" message in nand init
> which was okay before this git pull

But this is a different error message, isn;t it?

> > Is this with or without USE_PRIVATE_LIBGCC=yes ?
> Yes, the build might be with this defined "yes", without this build throws error message

Argh...

Could you please provide a usable error report?

Which exact tool chain is this? What are your exact commands to
configure and build the board? What are the exact error messages?

> This is openrd board, not yet mainlined, it is derived from sheevaplug, (na> nd is similar)
> Alternately you can refer sheevaplug.h since problem is on sheevaplug too.

I don;t see any error messages when building, and I don't have such a
board to actually run the code.

> I tried removing this patch and things are normal on sheevaplug

I wish you had reported such issues when the patch was posted. There
has been _long_ discussion about it.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?"

  reply	other threads:[~2009-08-24 11:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-17 11:17 [U-Boot] [PATCH] ARM: compiler options cleanup - improve tool chain support Wolfgang Denk
2009-08-17 13:00 ` Tom
2009-08-17 13:25   ` Wolfgang Denk
2009-08-17 15:26   ` Dirk Behme
2009-08-17 19:43 ` ksi at koi8.net
2009-08-17 20:17 ` Magnus Lilja
2009-08-17 20:27   ` Wolfgang Denk
2009-08-18 17:08     ` Magnus Lilja
2009-08-18 21:18       ` Wolfgang Denk
2009-08-18 11:06 ` Gaye Abdoulaye Walsimou
2009-08-18 11:22   ` Wolfgang Denk
2009-08-20 15:27   ` Andrzej Wolski
2009-08-18 11:45 ` Gaye Abdoulaye Walsimou
2009-08-18 18:50 ` Tom
2009-08-18 21:19   ` Wolfgang Denk
2009-08-21 21:12 ` Wolfgang Denk
2009-08-24  8:59   ` Simon Kagstrom
2009-08-24 10:01     ` Wolfgang Denk
2009-08-24 11:28       ` Prafulla Wadaskar
2009-08-24 11:56         ` Wolfgang Denk [this message]
2009-08-24 12:41           ` Prafulla Wadaskar
2009-08-24 12:59             ` Simon Kagstrom
2009-08-24 13:05             ` Wolfgang Denk
2009-08-24 11:38       ` Simon Kagstrom
2009-08-24 12:01         ` Wolfgang Denk
2009-08-24 12:49           ` Simon Kagstrom
2009-08-25  7:12       ` Simon Kagstrom
2009-09-04 20:05         ` Wolfgang Denk
2009-09-07  6:23           ` Simon Kagstrom
2009-09-07  8:59             ` Prafulla Wadaskar
2009-09-07  9:15               ` Simon Kagstrom

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=20090824115648.84C5C833DBD2@gemini.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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