From: 25an <mans.zigher@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!!
Date: Tue, 27 Feb 2007 06:23:03 -0800 (PST) [thread overview]
Message-ID: <9182852.post@talk.nabble.com> (raw)
In-Reply-To: <45E3FD8B.3030207@gmx.net>
I manged to solve the problem but now I get another one.
The first problem was solved by edit the cpu/arm926ejs/at91sam926x/config.mk
file
accordingly
#PLATFORM_CPPFLAGS += -mapcs-32 -march=armv5te -mtune=arm926ejs
PLATFORM_CPPFLAGS += -march=armv5te -Wa,-mapcs-32 -mtune=arm926ej-s
the first error was fixed by changing the -mtune option from arm926ejs till
arm926ej-s
the second error was fixed by changing -mapcs-32 with -Wa,-mapcs-32 this was
done after reading following post
http://www.at91.com/phpbb/viewtopic.php?t=2312
-mapcs-32 option generates code for a processor running with a 32-bit
program counter and conforming to the function calling standards for the
APCS 32-bit option
If interested in what APCS is google after ARM APCS.
the option -Wa,-mapcs-32 is doing the following
-Wa,option
Pass option as an option to the assembler. If option contains commas, it
is split into multiple options at the commas.
Now the error that I am getting is
usb_ohci.c: In function 'usb_lowlevel_init':
usb_ohci.c:1659: error: invalid lvalue in assignment
make[1]: *** [usb_ohci.o] Error 1
make[1]: Leaving directory
`/opt/x-compile/eldk/workingarea/u-boot-1.1.5_atmel_1.2/cpu/arm926ejs/at91sam926x'
make: *** [cpu/arm926ejs/at91sam926x/libat91sam926x.a] Error 2
Again any help is appreciated
Daniel Hobi wrote:
>
> Hi M?ns,
>
> On 27.02.2007 09:49, M?ns Zigher wrote:
>> Hi!
>>
>> I am trying to compile u-boot-1.1.5 for at91sam9261ek with arm926ejs
>> cpu. I am using the eldk
>> cross toolchain 4.1 which is using gcc 4.0.0.
>> When I try to compile u-boot I get following error
>>
>> [snip]
>>
>> Any ideas?
>
> Use the latest U-Boot sources from http://www.denx.de/en/Software/GIT.
>
>> I would also appreciate any suggestion how to locate the error since
>> right now I have not even managed to locate were the flag is set.
>
> The CPU-specific flags are set by including cpu/arm926ejs/config.mk in
> the Makefile.
>
> Regards,
> Daniel
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
>
--
View this message in context: http://www.nabble.com/Can%27t-Compile-u-boot-1.1.5_atmel_1.2%21%21-tf3299277.html#a9182852
Sent from the Uboot - Users mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-02-27 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 8:49 [U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!! Måns Zigher
2007-02-27 9:44 ` Daniel Hobi
2007-02-27 14:23 ` 25an [this message]
2007-02-27 15:15 ` Daniel Hobi
2007-02-27 15:41 ` 25an
2007-02-27 16:09 ` 25an
2007-02-28 11:35 ` 25an
-- strict thread matches above, loose matches on Subject: below --
2007-02-27 8:54 25an
2007-02-27 15:21 Daniel Hobi
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=9182852.post@talk.nabble.com \
--to=mans.zigher@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