From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] uboot on microblaze, compilation error
Date: Fri, 19 Mar 2010 08:21:08 +0100 [thread overview]
Message-ID: <4BA325E4.4090006@monstr.eu> (raw)
In-Reply-To: <201003182111.28112.vapier@gentoo.org>
Mike Frysinger wrote:
> On Thursday 18 March 2010 05:29:19 Michal Simek wrote:
>> Mike Frysinger wrote:
>>> On Wednesday 17 March 2010 14:36:38 Horst Gall wrote:
>>>> I try to compile an actual version of u-boot for xilinx microblaze.
>>>>
>>>> The linker ends with the error-message:
>>>> ... mb-ld.real:u-boot.lds:1: parse error
>>>>
>>>> In u-boot main-directory I found the file 'u-boot.lds':
>>>> OUTPUT_ARCH(1)
>>>> ENTRY(_start)
>>>> ...
>>>> cpu/1/start.o (.text)
>>>> ...
>>>>
>>>> When I change the "1" to "microblaze" it works:
>>>> OUTPUT_ARCH(microblaze)
>>>> ENTRY(_start)
>>>> ...
>>>> cpu/microblaze/start.o (.text)
>>>> ...
>>>>
>>>> After "make ...config" my modification is overwritten.
>>>> How can I fix this problem?
>>> add "#undef microblaze" to the top of board/xilinx/microblaze-generic/u-
>>> boot.lds
>> Mike is right. I expect you are using toolchain from EDK where the
>> problem is. Linux toolchain are ok.
>
> i dont think the toolchain is broken. this is standard gcc behavior for all
> arches. i would check the microblaze gcc port, but it doesnt seem to be
> mainlined at gcc.gnu.org, so ive lost interest.
Michael Eager takes care about. There is official updated branch at
http://gcc.gnu.org/viewcvs/branches/microblaze/
He is trying to add it to mainline repo but AFAIF he wasn't successful
yet. I don't know how gcc community works but it seems to me a little
closed.
Michal
> -mike
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2010-03-19 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 18:36 [U-Boot] uboot on microblaze, compilation error Horst Gall
2010-03-17 19:16 ` Wolfgang Denk
2010-03-17 23:08 ` Mike Frysinger
2010-03-18 9:29 ` Michal Simek
2010-03-19 1:11 ` Mike Frysinger
2010-03-19 7:21 ` Michal Simek [this message]
2010-03-19 16:59 ` Mike Frysinger
2010-03-21 20:00 ` Wolfgang Denk
2010-03-21 22:20 ` Mike Frysinger
2010-03-21 22:45 ` Wolfgang Denk
2010-03-22 6:54 ` Mike Frysinger
2010-03-22 11:18 ` Wolfgang Denk
2010-03-22 21:29 ` Mike Frysinger
2010-03-22 21:39 ` Wolfgang Denk
2010-03-22 21:53 ` Mike Frysinger
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=4BA325E4.4090006@monstr.eu \
--to=monstr@monstr.eu \
--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 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.