From: Nicolae T <microvis@cox.net>
To: buildroot@busybox.net
Subject: [Buildroot] u-boot compile error
Date: Thu, 10 Dec 2009 17:20:10 -0800 [thread overview]
Message-ID: <1260494410.17342.16.camel@RoadRunner> (raw)
In-Reply-To: <20091211004425.GR28375@buzzloop.caiaq.de>
It's for omap3_overo. I guess we don't needed necessarily (and use some
existing),but we thought building it would give us a full set of tools,
since BR should be able to make it, supposedly.
Thanks.
On Fri, 2009-12-11 at 08:44 +0800, Daniel Mack wrote:
> On Thu, Dec 10, 2009 at 04:03:55PM -0800, Nicolae T wrote:
> > We're getting following compile errors at u-boot build time, for which
> > we have no clue.
> > There must be something we do in setup that leads to that, but why
> > failing with compile error? Set up rather straightforward with BR built
> > cross-compile chain.
> > Anyhow, this is wrong and I think it should be looked into.
>
> Do you need to build U-Boot at all? If not, just switch it off.
>
> > make[2]: Entering directory
> > `/home/nicolae/buildroot7Dec/output/build/u-boot-2009.08/lib_arm'
> > /home/nicolae/buildroot7Dec/output/staging/usr/bin/arm-linux-uclibcgnueabi-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/nicolae/buildroot7Dec/output/build/u-boot-2009.08/include -fno-builtin -ffreestanding -nostdinc -isystem /home/nicolae/buildroot7Dec/output/staging/usr/bin/../lib/gcc/arm-linux-uclibcgnueabi/4.4.2/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux -mno-thumb-interwork -march=armv5 -Wall -Wstrict-prototypes -fno-stack-protector -o board.o board.c -c
> > board.c:127: error: inline function ?coloured_LED_init? cannot be
> > declared weak
> > board.c:129: error: inline function ?red_LED_on? cannot be declared weak
> > board.c:131: error: inline function ?red_LED_off? cannot be declared
> > weak
>
> Which board are you building U-Boot for? If you necessarily need to
> compile it from the sources, I'd suggest asking at the U-Boot ML,
> providing as much information as you can on how to provoke this.
>
> Daniel
>
next prev parent reply other threads:[~2009-12-11 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 0:03 [Buildroot] u-boot compile error Nicolae T
2009-12-11 0:44 ` Daniel Mack
2009-12-11 1:20 ` Nicolae T [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-11 13:37 Sagaert Johan
2009-12-11 18:07 ` Nicolae T
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=1260494410.17342.16.camel@RoadRunner \
--to=microvis@cox.net \
--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