From: Rob Herring <robherring2@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Microblaze and Sparc boards are broken because of common timer func
Date: Tue, 12 Nov 2013 07:46:21 -0600 [thread overview]
Message-ID: <5282312D.3050908@gmail.com> (raw)
In-Reply-To: <52821FD7.7000503@monstr.eu>
On 11/12/2013 06:32 AM, Michal Simek wrote:
> Hi Masahiro,
>
> On 11/12/2013 10:04 AM, Masahiro Yamada wrote:
>> Hello Michal
>>
>>
>>> This should be fixed by this patch - at least for microblaze.
>>>
>>> commit 65ba7add0d609bbd035b8d42fafdaf428ac24751 Author: Rob
>>> Herring <rob.herring@calxeda.com> Date: Fri Nov 8 08:40:43
>>> 2013 -0600
>>>
>>> time: add weak annotation to timer_read_counter declaration
>>>
>>> A weak annotation is needed in order to prevent link errors
>>> when get_ticks is overridden. This fixes sandbox build.
>>>
>>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>>
>> No. I tried both the current u-boot/master and commit
>> 65ba7add0d, but Microblaze board failed with the same error
>> message.
>>
>
> Look at this log - uboot section.
> http://www.monstr.eu/wiki/doku.php?id=log:2013-11-12_13_29_22
>
> Which toolchain do you use?
It builds for me with 4.8.0 from kernel.org, but I had to disable
systemace driver otherwise I get this error:
/opt/gcc-4.8.0-nolibc/microblaze-linux/bin/microblaze-linux-gcc -g
-Os -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x29000000
-I/home/rob/proj/git/u-boot-arm/include -fno-builtin -ffreestanding
-nostdinc -isystem
/opt/gcc-4.8.0-nolibc/microblaze-linux/bin/../lib/gcc/microblaze-linux/4.8.0/include
-pipe -ffixed-r31 -D__microblaze__ -mno-xl-soft-mul -mno-xl-soft-div
-mxl-barrel-shift -Wall -Wstrict-prototypes -fno-stack-protector
-Wno-format-nonliteral -Wno-format-security -fstack-usage -o
systemace.o systemace.c -c
systemace.c: In function 'ace_readw':
systemace.c:70:1: warning: stack usage computation not supported for
this target [enabled by default]
}
^
{standard input}: Assembler messages:
{standard input}:2499: Error: operation combines symbols in different
segments
{standard input}:2500: Error: operation combines symbols in different
segments
{standard input}:2503: Error: operation combines symbols in different
segments
{standard input}:2504: Error: operation combines symbols in different
segments
{standard input}:2509: Error: operation combines symbols in different
segments
{standard input}:2510: Error: operation combines symbols in different
segments
{standard input}:2519: Error: operation combines symbols in different
segments
{standard input}:2520: Error: operation combines symbols in different
segments
{standard input}:2523: Error: operation combines symbols in different
segments
{standard input}:2524: Error: operation combines symbols in different
segments
{standard input}:2533: Error: operation combines symbols in different
segments
{standard input}:2534: Error: operation combines symbols in different
segments
{standard input}:2537: Error: operation combines symbols in different
segments
{standard input}:2538: Error: operation combines symbols in different
segments
{standard input}:2543: Error: operation combines symbols in different
segments
{standard input}:2544: Error: operation combines symbols in different
segments
{standard input}:2553: Error: operation combines symbols in different
segments
{standard input}:2554: Error: operation combines symbols in different
segments
make[3]: *** [systemace.o] Error 1
Rob
next prev parent reply other threads:[~2013-11-12 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:12 [U-Boot] Microblaze and Sparc boards are broken because of common timer func Masahiro Yamada
2013-11-12 8:19 ` Michal Simek
2013-11-12 9:04 ` Masahiro Yamada
2013-11-12 12:32 ` Michal Simek
2013-11-12 13:46 ` Rob Herring [this message]
2013-11-12 15:37 ` Michal Simek
2013-11-18 13:24 ` Tom Rini
2013-11-18 13:50 ` Michal Simek
2013-11-14 0:37 ` Masahiro Yamada
2013-11-18 9:36 ` Michal Simek
2013-11-18 10:50 ` Masahiro Yamada
2013-11-18 10:53 ` Michal Simek
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=5282312D.3050908@gmail.com \
--to=robherring2@gmail.com \
--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