From: Daniel Hobi <dhobi@gmx.net>
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 16:21:01 +0100 [thread overview]
Message-ID: <45E44C5D.5070300@gmx.net> (raw)
Argh, ignoring the plain-text restriction myself. Sorry about that!
On 27.02.2007 15:23, 25an wrote:
> 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
I suggest not using -mtune at all, it will most likely not produce
different (more efficient) code than using -march=armv5te alone when
compiling U-Boot.
The gcc flag -mapcs-32 was deprecated since gcc-3.4.0 and finally
removed in gcc-4.0.0 which unconditionally generates 32bit ARM code. You
should not need to pass this flag to the assembler either.
> 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, update to a more recent version of U-Boot. Or, if that is not
possible, use an older toolchain/compiler (for example gcc-3.4.6 should
work with U-Boot 1.1.5).
U-Boot 1.1.5 DOES NOT WORK with gcc-4.x! Expect more (hidden) problems!
> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
Please post plain-text messages to this list.
Regards,
Daniel
next reply other threads:[~2007-02-27 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:21 Daniel Hobi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-27 8:54 [U-Boot-Users] Can't Compile u-boot-1.1.5_atmel_1.2!! 25an
2007-02-27 8:49 Måns Zigher
2007-02-27 9:44 ` Daniel Hobi
2007-02-27 14:23 ` 25an
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
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=45E44C5D.5070300@gmx.net \
--to=dhobi@gmx.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