From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] one warning left for all ARM boards
Date: Mon, 9 Jul 2012 17:42:10 +0200 [thread overview]
Message-ID: <20120709174210.0bc0cef5@aari01-12> (raw)
Hi all,
With the latest commits on u-boot/master, two obnoxious "attention"
messages were removed from ARM builds, but one still remains:
attention : -fstack-usage not supported for this target [enabled by
default]
This is with gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5).
doc/SPL/README.omap3 does indeed say that not all GCC releases have
-fstack-usage, and commit 4a30f1e8 from Tom Rini (Cc:) says it tests
for the option, but apparently testing for the option is not the same as
testing for the option on a given target...
How do we get rid of those warnings? Right now they appear for every
single ARM board built.
Amicalement,
--
Albert.
next reply other threads:[~2012-07-09 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:42 Albert ARIBAUD [this message]
2012-07-09 19:48 ` [U-Boot] [ARM] one warning left for all ARM boards Wolfgang Denk
2012-07-09 20:42 ` Tom Rini
2012-07-09 20:47 ` Albert ARIBAUD
2012-07-09 21:07 ` Tom Rini
2012-07-09 21:53 ` Albert ARIBAUD
2012-07-10 1:53 ` Marek Vasut
2012-07-10 8:37 ` Tom Rini
2012-07-10 8:46 ` Ilya Yanok
2012-07-10 8:52 ` Tom Rini
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=20120709174210.0bc0cef5@aari01-12 \
--to=albert.u.boot@aribaud.net \
--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